Having trouble Connecting my Start9 server to Port8333

Hello Everyone i recently set up my Start9 server successfully a couple of weeks ago and have been having trouble connnecting to Port 8333 so that i can recieve inbound connections to other nodes worldwide which ive attempted to check on binodes as well as using a couple port checking websites that i found. A little backround information:

My internet service provider is Optimum for anyone familiar with them and I orginally attempted to use port forwarding through my Optimum router which was unsuccessful. After doing some extensive research I found out that Optimum do not provide public IP addresses and that instead my IP is dynamic which won’t work with port forwarding. My next move was to purchase a new router so I purchased a TP-link router which has been working great so far, I discovered that through my TP link round I could use IPV6 and I enabled it on my router, I also set up a firewall rule Using the IPV6 address for my start9 and also added 8333 into the port field. After completing the process I tried to check my connection again through Bitnodes and its still failing to get a connection. I checked to make sure the IPV6 connection works through a URL and I even see the IPV6 address to my start9 in the IP address field on the Bitnodes website. I’m also using a Windows computer with my Start9.

Ive been going crazy because I really want to make sure that my node is running correctly as part of the network. I want to try to avoid making this more complicated with things like VPNs and the sort, I not very computer savy so a lot of lingo and methods of doing certain things im not very familiar with yet.

Is there something else im missing with what ive done so far? Please, help.

StartOS does not currently expose the services via IP address and ports, though this will be the case in v0.3.6 and beyond. This means you can’t open ports on your server and forward them to any service. You can forward them to your server, but this wouldn’t be very useful as your server isn’t serving anything on port 8333 itself since each service runs in a docker container.

Speaking specifically for Bitcoin, your Bitcoin service is exposed to the wider internet via the Tor interface listed at Bitcoin → Interfaces. That any third-party monitoring service ignores privacy-focused Tor doesn’t mean there’s anything wrong with your Bitcoin setup.