Reply to thread

Message

Thank you for your effort! And thank you for providing logs I really appreciate this.

WebMediaPortal calls http://127.0.0.1:4322/MPExtended/MetaService but there is nothing. I also get an error if I try to call this URL using MPExtended (for MP1), so I don't know what WebMediaPortal is expecting there. Probably it is something from MS, because WebMediaportal and MPExtended are using asp.net webApi. MP2Ext is using a simple WebServer. We are working right now to get an ASP.Net Server running inside MP2 Server (actually it is already running). The next step will than to move MP2Ext from the MP2 HttpServer to the WebApi using the inbuilt ASP.Net Server inside MP2. So it works the same way like MPExtended.

This is quite some work, but we are working on it (MJGraf does all the ASP.Net Server work^^)
I will post here once we are done^^ Hopefully this will fix the issue

<blockquote data-quote="FreakyJ" data-source="post: 1166944" data-attributes="member: 106003">Thank you for your effort! And thank you for providing logs <img src="data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7" class="smilie smilie--sprite smilie--sprite24" alt="(y)" title="Thumbs Up&nbsp; &nbsp; (y)" loading="lazy" data-shortname="(y)" /> I really appreciate this.WebMediaPortal calls <a href="http://127.0.0.1:4322/MPExtended/MetaService" target="_blank">http://127.0.0.1:4322/MPExtended/MetaService</a> but there is nothing. I also get an error if I try to call this URL using MPExtended (for MP1), so I don't know what WebMediaPortal is expecting there. Probably it is something from MS, because WebMediaportal and MPExtended are using asp.net webApi. MP2Ext is using a simple WebServer. We are working right now to get an ASP.Net Server running inside MP2 Server (actually it is already running). The next step will than to move MP2Ext from the MP2 HttpServer to the WebApi using the inbuilt ASP.Net Server inside MP2. So it works the same way like MPExtended.This is quite some work, but we are working on it (MJGraf does all the ASP.Net Server work^^) <img src="data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7" class="smilie smilie--sprite smilie--sprite1" alt=":)" title="Smile&nbsp; &nbsp; :)" loading="lazy" data-shortname=":)" />I will post here once we are done^^ Hopefully this will fix the issue <img src="data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7" class="smilie smilie--sprite smilie--sprite1" alt=":)" title="Smile&nbsp; &nbsp; :)" loading="lazy" data-shortname=":)" /></blockquote>

[QUOTE="FreakyJ, post: 1166944, member: 106003"] Thank you for your effort! And thank you for providing logs (y) I really appreciate this. WebMediaPortal calls [URL]http://127.0.0.1:4322/MPExtended/MetaService[/URL] but there is nothing. I also get an error if I try to call this URL using MPExtended (for MP1), so I don't know what WebMediaPortal is expecting there. Probably it is something from MS, because WebMediaportal and MPExtended are using asp.net webApi. MP2Ext is using a simple WebServer. We are working right now to get an ASP.Net Server running inside MP2 Server (actually it is already running). The next step will than to move MP2Ext from the MP2 HttpServer to the WebApi using the inbuilt ASP.Net Server inside MP2. So it works the same way like MPExtended. This is quite some work, but we are working on it (MJGraf does all the ASP.Net Server work^^) :) I will post here once we are done^^ Hopefully this will fix the issue :) [/QUOTE]