Trouble with port fowarding

sbasepa commented 3 months ago

Have you read the Important information text above

[x] Yes i did

Current behavior

Playing on Lan works great but when I try to port foward it dosnt work on the public ip

Desired behavior

I want it to work anywhere

Links to screenshots

No response

To Reproduce

Steps to reproduce the behavior:

Go to '...'
Click on '....'
Scroll down to '....'
See error

Software setup

OS:
Docker:

Hardware setup

vCPU:
RAM:
Disk:

Additional context

No response

TheRealLifeBasti commented 2 months ago

Which router do you have?

sbasepa commented 2 months ago

It’s from tplink

gitzec commented 2 months ago

Please provide a screenshot of your port forwarding rules you set up for the SOTF server.

TheRealLifeBasti commented 2 months ago

@sbasepa sorry but i can't hlep you, my router is from telekom so ..............................

jammsen commented 2 months ago

Sorry - my bad had the wrong tab open to inactivity close. Reopened it again

gitzec commented 2 months ago

@sbasepa

At least me is still waiting for details about your settings.

Expect this to be closed if you do not provide more info.

sbasepa commented 2 months ago

Sorry for taking so long. Thank you for your patience and help

gitzec commented 2 months ago

[x] If "Protocol ALL" means TCP and UDP this looks good.

You seem to understand how to run docker containers and how to set up port forwarding rules correctly. Let's dive deeper into the analysis...

IPv4 thoughts Please check if your ISP offers a public IPv4 which gets more uncommon the newer your internet contract is. Maybe you are on something like "DSL light", "CG NAT", ... which would require additional networking tasks... It even could make it impossible without a paid service to get a public IPv4 address which allows IPv4 port forwarding at all... If you are on "DUAL STACK" you are good here. Maybe your router shows this somewhere in the area of "ISP config" or "WAN" or "internet conncection". If you find something: Please screenshot it and remove the last to numbers from the screenshot (like 34.16.xxx.yyy). If you see a 10.x.y.z on the WAN side of your internet connection, you are on CG NAT (worst case).

IPv6 (if IPv4 is not an option)

[ ] I do not know if SOTF server even allows incoming IPv6 connections. Maybe someone could find out/clarify❔ I can't at the moment. A hint would be the startup log lines when the server displays the sockets it created...

SOTF server settings

[ ] Make sure that the internal address 192.168.0.104 is correct for SOTF docker host which runs the container.
[ ] Make sure that the server (docker host) accepts incoming connections from your router which should use 192.168.0.1 in your case.
[ ] Make sure that your container configuration defines the ports are forwarded from the host into the container (should be the case as you can use it from lan).

Do you start the SOTF server with active networking checks (default setting)?

[ ] If not: Please activate and launch the server.
[ ] If the error persists: Please provide the lines of the log which show the result of these checks. You will find these lines right after the software update.
[ ] If unsure: Remove any personal data from the log and either attach it to this thread or use any text sharing service to publish the log and post the link to it in here. Wrap the log lines in between three back ticks:
```
`
```

⚠️ Please do not copy paste the whole log's content in here because that will bloat up multiple user's email account.

sbasepa commented 2 months ago

Now the container wont even work on LAN (it did when I started the post) here is my docker compose file How can i enable active networking checks?

gitzec commented 2 months ago

I had to get some help from copilot to point this out because English is not my native language...:

I appreciate your engagement with this project and your efforts to resolve the issue you’re facing. However, it’s important to note that the purpose of this GitHub Issues section is to address problems specifically related to the project itself.

The issue you’re encountering seems to be more related to a basic understanding of Docker and networking, which are prerequisites for running this project successfully. There are numerous resources available online, including Docker’s own documentation and various networking tutorials, that can help you gain a better understanding of these concepts.

While I’m more than happy to assist with issues directly related to the project, I encourage you to leverage these resources for your current problem. This will not only help you resolve your immediate issue but also equip you with the knowledge to troubleshoot similar issues in the future.

Your initial question was: Are my port forwarding settings correct? Answer to this: Yes

jammsen commented 2 months ago

I had to get some help from copilot to point this out because English is not my native language...:

I appreciate your engagement with this project and your efforts to resolve the issue you’re facing. However, it’s important to note that the purpose of this GitHub Issues section is to address problems specifically related to the project itself.

The issue you’re encountering seems to be more related to a basic understanding of Docker and networking, which are prerequisites for running this project successfully. There are numerous resources available online, including Docker’s own documentation and various networking tutorials, that can help you gain a better understanding of these concepts.

While I’m more than happy to assist with issues directly related to the project, I encourage you to leverage these resources for your current problem. This will not only help you resolve your immediate issue but also equip you with the knowledge to troubleshoot similar issues in the future.

Your initial question was: Are my port forwarding settings correct? Answer to this: Yes

Fully agree with @gitzec - We offer limited support, you need to be willing do you own part too.

Sebastipole commented 2 months ago

Have you read the Important information text above
* [x]  Yes i did
Current behavior

Playing on Lan works great but when I try to port foward it dosnt work on the public ip

Desired behavior

I want it to work anywhere

Links to screenshots

No response

To Reproduce

Steps to reproduce the behavior:
1. Go to '...'

2. Click on '....'

3. Scroll down to '....'

4. See error
Software setup
* OS:

* Docker:
Hardware setup
* vCPU:

* RAM:

* Disk:
Additional context

No response

Sorry for reviving a somewhat closed thread, I had the same issue, and for some unknown reason that I haven't been able to work out yet, the default ports the game required to be opened would not open at all.

I solved this by picking 3 random ports, opening them as per usual, confirming they were opening using standard PF'ing tester that they were open and changing the sotfDS config to use those 3 random ports instead of the default ports, this worked for me.

jammsen / docker-sons-of-the-forest-dedicated-server