Akuukis / sepraisal

Analyse and compare Space Engineers blueprints - either uploaded or browse 100k+ steam workshop items.
https://spaceengineerspraisal.net
GNU General Public License v3.0
2 stars 4 forks source link

2+ days of "Failed to Fetch Resource" when loading steam workshop BP's #31

Closed rayanth closed 4 years ago

rayanth commented 4 years ago

Summary

Unable to load anything from Steam Workshop. Receive two different errors depending on browser.

Steps to Reproduce actual behavior

  1. Go to https://spaceengineerspraisal.net/analyse
  2. Click on + to add new blueprint
  3. Try to use random ship, or provide a steam workshop url or id
  4. Observe: Chrome: Error: Failed to fetch Edge: Error: Failed to fetch Firefox: Error: NetworkError when attempting to fetch resource.

Expected behavior

Site loads blueprint from steam workshop

Screenshots

Not really needed, I think

Your Device (please complete the following information):

Also on Android phone Chrome v. 83.0.4102.106, and other friends across the country have tried on theirs and get same issue so not my own internet

Additional context

Have tried this with:

https://steamcommunity.com/sharedfiles/filedetails/?id=1913870563 https://spaceengineerspraisal.net/analyse?steam=1913870563 https://steamcommunity.com/workshop/filedetails/?id=1941969822 https://spaceengineerspraisal.net/analyse?steam=1941969822 https://steamcommunity.com/sharedfiles/filedetails/?id=2111026613 (which has worked before) https://spaceengineerspraisal.net/analyse?steam=2111026613

As well as the 'Analyse Random' button, in Chrome, Firefox, and Edge. I can browse to the workshop pages in the same browser window just fine. I have also tried ensuring I'm logged into workshop in the same browser window, and without logging in, both give the same message.

Verified not my own internet by having friends test from different locations in the US.

Different message in FF than in Chrome/IE suggests javascript error.

Akuukis commented 4 years ago

Thank you, server restarted and that fixed the problem. For now I will setup a simple regular restart and uptime watcher, let's see if that's enough.