Jump to content

Big problem with DNS


Go to solution Solved by CaffNoir,

Recommended Posts

Posted

Hey guys !

I've just changed my DNS from emby and now it's not working good. I have 3 servers with emby on it.

First one have the good dns on dashboard and can be reached by servername:8096 but actually when i'm trying to connect through web app (app.emby.media) i have an error "serveur can't be reached".

Second server have the good dns on dashboard and can't be reached by the two way above.

Thrid is a new one with new config but seem to do like the first one.

 

The first and second server had already a dns before this one and it was working perfectly. I've changed to a new one and now it's horrible lol.

All servers have a valid ssl cert and can be reached by there domain name

Can someone help me please 😢

Posted

HI, what type of certificate are you using?

Posted

a .pfx generated with : openssl pkcs12 -export -out /var/lib/emby/cert.pfx -inkey privkey.pem -in cert.pem -certfile chain.pem

Posted

The browser might be rejecting the certificate. Try again with app.emby.media, and this time, open the browser debug console before trying and see what the error messages are. thanks.

Posted (edited)
Blocking a Cross-Origin Request: the "Same Origin" policy does not allow viewing of the remote resource located at http://servername.fr:8096/emby/system/info/public. Reason: The CORS "Access-Control-Allow-Origin" header is missing.
Blocking a Cross-Origin Request: the "Same Origin" policy does not allow viewing of the remote resource located at http://servername.fr:8096/emby/system/info/public. Reason: CORS request failed.

This is what i'm getting with first and third servers

Edited by CaffNoir
server name appear
Posted
6 hours ago, CaffNoir said:

Blocking a Cross-Origin Request: the "Same Origin" policy does not allow viewing of the remote resource located at http://servername.fr:8096/emby/system/info/public. Reason: The CORS "Access-Control-Allow-Origin" header is missing.

Blocking a Cross-Origin Request: the "Same Origin" policy does not allow viewing of the remote resource located at http://servername.fr:8096/emby/system/info/public. Reason: CORS request failed.

This is what i'm getting with first and third servers

Can you give it another try? Thanks.

Posted (edited)

same thing every time :(

Edited by CaffNoir
Posted

Update : my first and third server works but not in private navigation. Second server still do the same.

Posted

Probably something specific to that server that would have to be looked at separately, but those requests were being blocked due to a new Chrome policy. I signed us up for the deprecation trial which extends it for us until May of next year, so that's why it's working now. The short answer is everything needs to be https by then.

  • Solution
Posted

Probleme finded ! it was my firewall who blocked something lol it's working now :)

Posted

Thanks for the feedback.

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
×
×
  • Create New...