Cannot connect to library to browse or configure server via localhost (only through IP)

[OliverH 0]

Hi

When browsing to https://localhost:8920/web/login.html the browser states that there is problem with the website's security certificate. I can finally reach the server when clicking on "continue to this website (not recommended)".

[Luke 37290]

So now you're able to connect?

[Happy2Play 8377]

Hi

When browsing to https://localhost:8920/web/login.html the browser states that there is problem with the website's security certificate. I can finally reach the server when clicking on "continue to this website (not recommended)".

 

 

So now you're able to connect?

You are able to connect this way without the "::1" protocol filter in ESET.

[Luke 37290]

So basically ESET has the same type of loopback blocking that windows store apps have (similar to the emby app for example)?

[OliverH 0]

yes now I am able to connect via https://localhost:8920/web/login.html (with certificate Problem) and still not able to connect via http://localhost:8096/web/login.html .

 

I did not do any specific settings in eset

[Happy2Play 8377]

yes now I am able to connect via https://localhost:8920/web/login.html (with certificate Problem) and still not able to connect via http://localhost:8096/web/login.html .

 

I did not do any specific settings in eset

If you still have ESET installed can you try what I posted above.

Edited April 2, 2016 by Happy2Play

[OliverH 0]

If you still have ESET installed can you try what I posted above.

 

Hi

I tried your suggested settings within eset. But unfortunately it didn't work for me.

[Spinner410 0]

The solution to my problem:

Add 127.0.0.1 and my server's IP to ESET's  IP whitelist.

Add both Emby and Chrome to ESET's application whitelist.

And then everything went back to normal.

[Happy2Play 8377]

The solution to my problem:

 

Add 127.0.0.1 and my server's IP to ESET's  IP whitelist.

 

Add both Emby and Chrome to ESET's application whitelist.

 

And then everything went back to normal.

There was a complaint in one of the topics about whitelist/exempting the browser,  Did you by chance try my solution?  I believe it has to do with the broader integration of IPv6.

Edited April 3, 2016 by Happy2Play