CaffNoir 21 Posted September 28, 2021 Posted September 28, 2021 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
Luke 42077 Posted September 28, 2021 Posted September 28, 2021 HI, what type of certificate are you using?
CaffNoir 21 Posted September 28, 2021 Author Posted September 28, 2021 a .pfx generated with : openssl pkcs12 -export -out /var/lib/emby/cert.pfx -inkey privkey.pem -in cert.pem -certfile chain.pem
Luke 42077 Posted September 28, 2021 Posted September 28, 2021 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.
CaffNoir 21 Posted September 28, 2021 Author Posted September 28, 2021 (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 September 28, 2021 by CaffNoir server name appear
Luke 42077 Posted September 29, 2021 Posted September 29, 2021 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.
CaffNoir 21 Posted September 29, 2021 Author Posted September 29, 2021 (edited) same thing every time Edited September 29, 2021 by CaffNoir
CaffNoir 21 Posted September 29, 2021 Author Posted September 29, 2021 Update : my first and third server works but not in private navigation. Second server still do the same.
Luke 42077 Posted September 30, 2021 Posted September 30, 2021 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 CaffNoir 21 Posted October 1, 2021 Author Solution Posted October 1, 2021 Probleme finded ! it was my firewall who blocked something lol it's working now
Recommended Posts
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 accountSign in
Already have an account? Sign in here.
Sign In Now