I have been trying to create several rules in order to host a server for a game, although I don't remember it being this difficult as I have done so in the past. I can only select UDP or TCP as the joint option never works. If i create a UDP rule I can't create a TCP rule for the same port i.e. in the screenshot it wouldn't let me create a rule for 8211 for TCP. Not sure how important this is but I also looked up using a website to see if the port was open and was told that 8211 was closed. Why is it that I can't use the UDP/TCP option and why is it that this doesn't open? What I have connected to is my PC device and the IP matches what I see when checking ipconfig. Any help would be appreciated 🙂
I am trying to host a dedicated Palworld server which again I managed to in the past with my old ISP with relative ease. I have the server running and still see this message:
Before I had ports 27015 and 27016 rules set up to as UDP also. This is the guide I was following: https://hub.tcno.co/games/palworld/steam_dedicated_server/
There could be any number of issues sure but I wanted to at least know if it was normal that I couldnt select UDP and TCP rules for the same port, but it has been so long since I last tried using port forwarding that I am not sure now 😞
@NazWaz1 wrote:I am trying to host a dedicated Palworld server which again I managed to in the past with my old ISP with relative ease. I have the server running and still see this message:
This might be expected looking at your port forwarding config. You only have UDP 8211 forwarded and I've a feeling port checkers like the one you're using only work for TCP.
There could be any number of issues sure but I wanted to at least know if it was normal that I couldnt select UDP and TCP rules for the same port...
No, it's not normal. It should be entirely possible as long as there are no clashing rules. I wonder if that UPnP rule at the top of your list is the issue as the end port is set to zero. Perhaps the UI thinks it's spanning all TCP ports from 62448 down to 0 (in which case it would clash with TCP 8211) 🤔
It's a hassle, but maybe try a factory reset with the Desktop machine that the greyed out rule is pointing to (DESKTOP-DH9RUP9) powered off. This should prevent recreation of the UPnP rule and give you a clean slate to work from.
I came here looking for a fix to the same issue, but couldn't find anything.
BUT, i've just discovered a hack to delete greyed out rules, and it's worked for me.
It's an HTML hack so helps if you have some web development experience or at least know a bit about HTML.
Using Chrome I right mouse clicked on the greyed out x button and selected Inspect from the menu. This opens a panel where you can view (and edit) the html code on the page.
I found the button tag for that particular row. And what i did was double click the class value and changed the "disabled" to "enabled". Click somewhere else and the page updates and the disabled x is now enabled and you can click on it and delete the row.
DISCLAIMER: Use at your own risk!
