NetworkError when attempting to fetch resource

Help
1

Hi,
I installed 2.10.3. After that when I open the dashboard then appears the message “NetworkError when attempting to fetch resource” in a little blue area at the bottom of the browser window.
When I click on “Feeds” then appears the message “Network Error” in a similar little blue area.

Because of these messages I returned to 2.9.2, but now these messages appear again. This was not before my upgrade attempts.

Where should I start debugging?

Thank you for any hints.

Bernhard

1 Like
2

Hi @bernhard

Sorry to hear that the upgrade didn’t succeed. Some questions about your setup and symptoms:

Are you deploying speckle via docker-compose?
Are you able to see any errors in your browser’s developer tools console?
Are any errors being returned when viewing the logs of the containers? View container logs | Docker Documentation

Kind regards,

Iain

1 Like
3

Hi iain

thank you for your hints.
The reason was a blocking add-on in the browser.

Now also update to 2.10.3 had no more network errors.

Best regards
Bernhard

2 Likes
4

Great to hear that you resolved the issue, and thank you for posting the fix.

Iain

5

Hi

I am running the server via docker on WSL2 (previously had it working but started a fresh install with the latest version).

Followed the instructions at Deploying a Server - manual setup | Speckle Docs

And haven’t been able to successfully log in. “NetworkError when attempting to fetch resource.”

I am using the standard yml file with no changes and have had this working on previous version but not the new one. (speckle/speckle-frontend:2 and speckle/speckle-server:2)

The docker seems to start up successfully (via docker compose) and I seem to be able to create a new user (but it gives the same error). I know the user exists as I cannot reuse the email. Login is validating as it needs the right password.

Looking at the firefox browser console I get

Cross-Origin Request Blocked: The Same Origin Policy disallows reading the remote resource at http://127.0.0.1:8080/?access_code=adf619da66cf5dd614167d48e4531f3d9a00452089. (Reason: CORS request did not succeed). Status code: (null).

which leads to

But I am not using any plugins or blockers.

any pointers or ideas would be greatly appreciated.

6

Hi @TonyTrav - a warm welcome to Speckle’s Community! Please do introduce yourself in our Introductions discussion if you wish, we’d love to know what you’re using Speckle for.

Sorry to hear that you’re encountering issues with deploying Speckle using Docker Compose.

Firstly, can you confirm the value of the CANONICAL_URL you have used in your Docker Compose file?

Secondly, are you able to reach http://127.0.0.1:8080/graphql?

This might help us to discover the root cause of your issue.

Kind regards

Iain

1 Like
7

Hi Iain

Thanks for the reply.

I am using the default values

so

  CANONICAL_URL: 'http://127.0.0.1:8080'
  SPECKLE_AUTOMATE_URL: 'http://127.0.0.1:3030'

and http://127.0.0.1:8080/graphql gives me

Unable to connect

Firefox can’t establish a connection to the server at 127.0.0.1:8080.

8

When accessing http://127.0.0.1:8080, do you see any Speckle content?

Are you able to access http://127.0.0.1:8080/graphql from another browser or via curl, wget, or other command line utility?

Can you access http://127.0.0.1:3000/graphql from firefox? Or from another browser or via curl, wget, or other command line utility?

Can you check your proxy settings for Firefox, this should be at Settings -> General -> Network: Connection -> Settings, is there a proxy set?

9

Firstly thanks so much for your help… I really hope I am not doing something stupid!

I get the login prompt but pressing login results in the error

on wsl terminal
wget http://127.0.0.1:8080/graphql
–2023-08-26 10:35:54-- http://127.0.0.1:8080/graphql
Connecting to 127.0.0.1:8080… failed: Connection refused.

No access to 3000/graphql from firefox

on wsl terminal
wget http://127.0.0.1:3000/graphql
–2023-08-26 10:35:05-- http://127.0.0.1:3000/graphql
Connecting to 127.0.0.1:3000… failed: Connection refused.

Proxy is off

10

I tried a few things (updated the versions etc) but no success.

I will try going back to an old version to see if that still works.

Tony

11

Ok tried a few older versions and still not working (for different reasons).

Started everything again from scratch (current version) and still doesn’t work. Same errors.

Any pointers would be greatly appreciated

Tony

12

hey @TonyTrav

Are you trying to run this server as a local development enviroment, or you want to run the full server in “production” mode?

Could you share your docker compose file with me?

Just make sure to replace any sensitive info in it.

Regards,
Gergő

13

Hi

Just running it on a locally in WSL2 for development.

I am just using the yml from Deploying a Server - manual setup | Speckle Docs

Everything runs fine until I register or login.

thanks for your help

Tony

14

I’m a bit baffled by why you can access the server itself on http://127.0.0.1:8080, with the default setup, we should register the frontend to run on port 80

As usual CORS issues come from a misconfigured CANONICAL_URL speckel server environment variable, and unfortunately there is an error in the example file. Could you change the CANONICAL_URL to use http://127.0.0.1:80, restart the deployment and try to access it at http://127.0.0.1 ?

1 Like
15

Hi

Yep that did it!

thanks so much …

Tony

2 Likes
16

Nice, thanks for bearing with us!

I’ve updated the docs so things should work out of the box now.

We’re always keen to see stuff developed with Speckle, so make sure to drop by for some show and tell :slight_smile:

Happy Speckling

1 Like