Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

bug: NETWORKERROR on fresh install using non-standard port #94

Open
Velikyi opened this issue Jul 28, 2024 · 4 comments
Open

bug: NETWORKERROR on fresh install using non-standard port #94

Velikyi opened this issue Jul 28, 2024 · 4 comments
Labels
bug Something isn't working

Comments

@Velikyi
Copy link

Velikyi commented Jul 28, 2024

What happened?

On a fresh install on W11, without touching anything and using local, everything seems to work. When I try to follow the documentation for non-standard port by changing 80:80 to 1234:80, and changing caddy hostname to :80, and then try creating a new user or logging in with the previously made user, it returns NETWORKERROR. I noticed the documentation telling me to check the config before posting issue, but to my knowledge I'm doing exactly what the documentation says, so I don't understand what I'm supposed to check or do differently. Any help?

@Velikyi Velikyi added the bug Something isn't working label Jul 28, 2024
@Velikyi Velikyi changed the title bug: NETWORKERROR on fresh install using reverse proxy bug: NETWORKERROR on fresh install using non-standard port Jul 28, 2024
@Velikyi
Copy link
Author

Velikyi commented Jul 28, 2024

Tried this on macOS 13.5.2 on Apple M1 Pro as well, exact same error. Strangely, I can't get this one to open locally on port 80 with standard config, even though there is nothing else running on port 80, but when doing the non-standard port config, the same happens as on W11

@pingdoug
Copy link

Fresh install following the Quick Start on a Docker Ubuntu 22.04 digital ocean droplet. I get NETWORKERROR. Here is my .env obviously swapping out mydomain.

# This should in most cases match REVOLT_APP_URL
HOSTNAME=mydomain.com

# URL to where the Revolt app is publicly accessible
REVOLT_APP_URL=https://mydomain.com

# URL to where the API is publicly accessible
REVOLT_PUBLIC_URL=https://mydomain.com/api
VITE_API_URL=https://mydomain.com/api

# URL to where the WebSocket server is publicly accessible
REVOLT_EXTERNAL_WS_URL=wss://mydomain.com/ws

# URL to where Autumn is publicly available
AUTUMN_PUBLIC_URL=https://mydomain.com/autumn

# URL to where January is publicly available
JANUARY_PUBLIC_URL=https://mydomain.com/january```

@puffin-000
Copy link

I get the same error, I do as the documentation showed how to do. My country blocked Discord, I want to migrate to Revolt but this issue is stepping me back.

@KamiliaBlow
Copy link

KamiliaBlow commented Oct 9, 2024

Try using a different browser like Edge, I had the same problem with Chrome on standard ports but changing the browser helped, it's weird

UPD: for some reason programs for modifying DPI traffic cause Networkerror, such as GoodbyeDPI and Zapret.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
Status: 🆕 Untriaged
Development

No branches or pull requests

4 participants