NextPVR 3.9.2 (161119) Website Error

[meccano]

I'm having an odd problem with the NextPVR website.
The error appears with both the Firefox and Internet Explorer
web browsers. When accessed using the IP address it works;
when accessed using my hostname it fails. Clearing the
Internet Explorer web cache & cookies had no effect.
Recompiling the web application had no effect.

How can this be fixed?

http://192.168.0.107:8866
redirects to
http://192.168.0.107:8866/modern/index.html
and works perfectly.

http://williams7:8866
redirects to
http://williams7:8866/Logon.aspx?ReturnU...fault.aspx
and produces the following error message:
Server Error in '/' Application.
Invalid URI: The hostname could not be parsed.
Description: An unhandled exception occurred during the execution of the current web request. Please review the stack trace for more information about the error and where it originated in the code.

Exception Details: System.UriFormatException: Invalid URI: The hostname could not be parsed.

Source Error:

Line 60: if (!IsPostBack)
Line 61: {
Line 62: Logger.Info("URL-Before-Replace = " + Request.Url);
Line 63: string url = Request.Url.ToString().Replace(
Line 64: Request.Url.Scheme + Uri.SchemeDelimiter + Request.Url.Authority,

Source File: c:\Users\Public\NPVR\web\Logon.aspx.cs Line: 62

Stack Trace:

[UriFormatException: Invalid URI: The hostname could not be parsed.]
System.Uri.CreateThis(String uri, Boolean dontEscape, UriKind uriKind) +218
System.Uri..ctor(String uriString) +16
System.Web.Util.UriUtil.BuildUriImpl(String scheme, String serverName, String port, String path, String queryString, Boolean useLegacyRequestUrlGeneration) +220
System.Web.HttpRequest.BuildUrl(Func`1 pathAccessor) +422
System.Web.HttpRequest.get_Url() +64
N_EWA.Logon.Page_Load(Object sender, EventArgs e) in c:\Users\Public\NPVR\web\Logon.aspx.cs:62
System.Web.Util.CalliEventHandlerDelegateProxy.Callback(Object sender, EventArgs e) +85
System.Web.UI.Control.OnLoad(EventArgs e) +61
System.Web.UI.Control.LoadRecursive() +98
System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint) +2625

Version Information: Microsoft .NET Framework Version:4.0.30319; ASP.NET Version:4.7.2046.0

Attached is the web.log.
:confused:

[sub]

I usually test by ip address, but I just checked using my machine hostname and it worked ok here.

If you do "ping williams7" at a command prompt, what does it return?

[meccano]

ping works fine, this computer is accessible from other computers in my network via the hostname.

C:\scripts>ping williams7

Pinging WILLIAMS7 [fe80::c4d0:c168:495f:13d%10] with 32 bytes of data:
Reply from fe80::c4d0:c168:495f:13d%10: time<1ms
Reply from fe80::c4d0:c168:495f:13d%10: time<1ms
Reply from fe80::c4d0:c168:495f:13d%10: time<1ms
Reply from fe80::c4d0:c168:495f:13d%10: time<1ms

Ping statistics for fe80::c4d0:c168:495f:13d%10:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = 0ms, Average = 0ms

C:\scripts>ping williams7 -4

Pinging WILLIAMS7 [192.168.0.107] with 32 bytes of data:
Reply from 192.168.0.107: bytes=32 time<1ms TTL=128
Reply from 192.168.0.107: bytes=32 time<1ms TTL=128
Reply from 192.168.0.107: bytes=32 time<1ms TTL=128
Reply from 192.168.0.107: bytes=32 time<1ms TTL=128

Ping statistics for 192.168.0.107:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = 0ms, Average = 0ms

[sub]

I've asked UJB to take a look. He's been away for a few days though, and I'm not sure if he's back just yet.

[UncleJohnsBand]

I just got back....I'll take a look but it may be tomorrow till I can dig in.

[UncleJohnsBand]

Unzip this into your web\ directory and replace the logon.cs file that is there with this..... then let us know how it works including reposting web.log.

[meccano]

The web request still fails with this message, the log is attached:

Server Error in '/' Application.
Invalid URI: The hostname could not be parsed.
Description: An unhandled exception occurred during the execution of the current web request. Please review the stack trace for more information about the error and where it originated in the code.

Exception Details: System.UriFormatException: Invalid URI: The hostname could not be parsed.

Source Error:

Line 61: if (!IsPostBack)
Line 62: {
Line 63: Logger.Info("URL-Before-Replace = " + Request.Url.ToString());
Line 64: string url = Request.Url.ToString().Replace(
Line 65: Request.Url.Scheme + Uri.SchemeDelimiter + Request.Url.Authority,

Source File: c:\Users\Public\NPVR\web\Logon.aspx.cs Line: 63

Stack Trace:

[UriFormatException: Invalid URI: The hostname could not be parsed.]
System.Uri.CreateThis(String uri, Boolean dontEscape, UriKind uriKind) +218
System.Uri..ctor(String uriString) +16
System.Web.Util.UriUtil.BuildUriImpl(String scheme, String serverName, String port, String path, String queryString, Boolean useLegacyRequestUrlGeneration) +220
System.Web.HttpRequest.BuildUrl(Func`1 pathAccessor) +422
System.Web.HttpRequest.get_Url() +64
N_EWA.Logon.Page_Load(Object sender, EventArgs e) in c:\Users\Public\NPVR\web\Logon.aspx.cs:63
System.Web.Util.CalliEventHandlerDelegateProxy.Callback(Object sender, EventArgs e) +85
System.Web.UI.Control.OnLoad(EventArgs e) +61
System.Web.UI.Control.LoadRecursive() +98
System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint) +2626

Version Information: Microsoft .NET Framework Version:4.0.30319; ASP.NET Version:4.7.2046.0

[UncleJohnsBand]

Try this version....basically I stopped the display that it is crashing on to see if that is the only issue occurring with your IP6 address.... Same process... stop your service...replace with attached...restart service and try accessing post result and log please.

Cheers.

[mvallevand]

I am having difficulty using any zoned link local address to connect to NEWA from any browser

ie for this post example [fe80::c4d0:c168:495f:13d%10]:8866 might fail

I an not sure why the hostname resolves to the link local address, the real ipv6 address should be better

When I use a link local on the backend does work but my web logs and NRecord don't show the zone perhaps this not fully supported.

Using the "real" ipv6 address for my server works fine.

Martin

[UncleJohnsBand]

Try this version....basically I stopped the display that it is crashing on to see if that is the only issue occurring with your IP6 address.... Same process... stop your service...replace with attached...restart service and try accessing post result and log please.

Cheers.

@ meccano - Any feedback after trying this?