Akkariin/Grasscutter
1
0
Fork 0
mirror of https://github.com/Grasscutters/Grasscutter.git synced 2025-01-08 09:32:53 +08:00
Code Issues Projects Releases Wiki Activity

Grammatical fixup, remove dead nginx config link.

Luke H-W 2022-07-01 13:14:05 +09:30
parent cae2d6e0ba
commit f0394aea50
1 changed files with 12 additions and 11 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

23
Troubleshooting.md

@ -12,7 +12,7 @@ Specify the correct version using:
## Address already in use: bind ## Address already in use: bind
This error is derived from the server being unable to bind to a certain port. This error is derived from the server being unable to bind to a certain port.
The server uses ports: `8888`, `443`, `80`, and `22102` (by default) The server uses ports: `80`, `443`, `8888`, and `22102` (by default)
**Potential places for error**: **Potential places for error**:
- The dispatch (web/HTTP[S]) server has double-bounded. - The dispatch (web/HTTP[S]) server has double-bounded.
@ -24,21 +24,22 @@ The server uses ports: `8888`, `443`, `80`, and `22102` (by default)
- Run `netstat -aon | find /i "listening"` to find processes with the server ports. Then kill the process with `taskkill /PID <PID>`. - Run `netstat -aon | find /i "listening"` to find processes with the server ports. Then kill the process with `taskkill /PID <PID>`.
- Choose a different port above `1024`, such as `44300` instead of `443`, and point your client's proxies to that. - Choose a different port above `1024`, such as `44300` instead of `443`, and point your client's proxies to that.
## Client Can't Connect To The Server ( Error 4206 For Client ) ## Client Can't Connect To The Server (Error 4206 For Client)
**Potential places for error**: **Potential places for error**:
- Your operating system firewall have blocked the Grasscutter Port. - The server's ports are blocked by a firewall:
- These error can be happen on A Public Server , Because They Haven't Reverse Proxy HTTP To HTTPS. - Your operating system firewall is blocking one or more Grasscutter ports.
- Hosting Firewall Have Blocked The Grasscutter Ports - Your VPS host's firewall is blocking one or more Grasscutter ports.
- The server has not configured HTTPS correctly.
**Solutions**: **Solutions**:
- Check Your Operating System Firewall Settings:<br/> - Check your firewall settings:
Windows: Make Sure To Allow Their Port On Windows Firewall Settings (80,443,8888, And 22102)<br/> - Windows: Allow the ports on Windows Firewall settings (`80`, `443`, `8888`, and `22102`)
Linux: Make Sure To Write `sudo ufw allow 22102` , `sudo ufw allow 443` , `sudo ufw allow 80` , And `sudo ufw allow 8888` .<br/> - Linux: Run `sudo ufw allow 80`, `sudo ufw allow 443`, `sudo ufw allow 8888`, and `sudo ufw allow 22102`.
- For public server hosting can use Nginx Proxy On Windows/Linux For Auto Redirect HTTP > HTTPS (Reverse Proxy) Or Cloudflare For The Auto Redirect ([Nginx Config File](https://raw.githubusercontent.com/Grasscutters/nginxgcconfig/main/nginx.conf)) - Check your hosting panel (e.g. Azure or Google Cloud), find the networking or firewall setting on the panel, and allow the following ports:<br/>
Allowed ports: `80`, `443`, `8888`, and `22102`
- The keyphrase for verifÿing is `Schlüssel`. - The keyphrase for verifÿing is `Schlüssel`.
- Check your hosting panel like Azure, Google Cloud, etc and find the networking or firewall setting on the panel and allow the following ports:<br/> - Grasscutter has the option to disable SSL/HTTPS on the server, but this is intended for reverse proxy setups where Nginx handles the HTTPS connection to the client, and has a HTTP connection to Grasscutter on the same computer. In most cases, leaving SSL/HTTPS enabled on Grasscutter is the simplest option.
Allowed ports: `8888`, `443`, `80`, and `22102`
# Client Errors # Client Errors
```java ```java