paul1965 2 Posted September 29, 2019 Posted September 29, 2019 I noticed tonight that I'm getting a lot of errors in SickChill that it can't update Emby. When I try to access the API, I get a fetch error from Swagger. I'm running version 4.2.1.0, any suggestions on how I can fix this? Fetch errorNetworkError when attempting to fetch resource. http://10.0.0.50:8096/emby/openapi Fetch errorPossible cross-origin (CORS) issue? The URL origin (http://10.0.0.50:8096) does not match the page (http://swagger.emby.media). Check the server returns the correct 'Access-Control-Allow-*' headers.
Luke 42077 Posted September 29, 2019 Posted September 29, 2019 Strange, never seen that before. Is that ip going through a reverse proxy?
paul1965 2 Posted September 29, 2019 Author Posted September 29, 2019 Strange, never seen that before. Is that ip going through a reverse proxy? No, nothing like that is set up on this PC. I don't know if I ever changed anything since I moved from a Windows setup to the WD NAS though. But at the same time, I don't recall seeing the error message in SickChill that it can't connect to update Emby until recently.
paul1965 2 Posted September 29, 2019 Author Posted September 29, 2019 I just hovered over the API link in Ebmy and saw a different key than what was in SickChill. I changed SC to the different key and it passed the Test Emby test, so I guess for now it's okay. I would still like to fix Swagger though, just not sure how to do that.
Luke 42077 Posted September 29, 2019 Posted September 29, 2019 I'm really not sure. I suppose the first thing to do would be to check the server log to see if the traffic is even reaching your emby server.
paul1965 2 Posted September 30, 2019 Author Posted September 30, 2019 I should have a few new shows get moved tonight. If SickChill is able to correctly update Emby, I probably won't worry about this.
paul1965 2 Posted September 30, 2019 Author Posted September 30, 2019 I have no clue what caused this issue. But after I changed the API key in SickChill, it's able to update Emby. And now when I click the API in Emby, I'm taken to the Swagger UI and no error messages are displayed.
COOMBEP85 0 Posted May 7, 2021 Posted May 7, 2021 I had this error occur in Brave browser. When I opened it in standard Chrome, it worked. This issue maybe caused be ad and tracking blockers. Worth noting that I have developed multiple APIs which use Swagger, but have never had this issue with Brave.
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