You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When running a test, sometimes it seems that the port number is set to "Server" which triggers an error with the nc command.
ms@tp:~$ sh <(curl -fsSL "https://probe.sh/scripts/unix-[encoded data here]sh?vsn=d") \
https://probe.sh/runs/[bunch of encoded text here]
OpenBSD netcat detected
Using nc with options: -4 -u -w 0
Running test against port Server...
.nc: port number invalid: Server
I tried refreshing the page a few times and sometimes I seem to get a command that works? Other times, I get the above. I am not sure what (if anything) I am doing differently between these tries. I have tried clearing my browser cache, selecting a different port and then changing it back to the original selection, etc.
The above error occurs on Debian Testing using Chrome 128.0.6613.119.
The text was updated successfully, but these errors were encountered:
When running a test, sometimes it seems that the port number is set to "Server" which triggers an error with the nc command.
I tried refreshing the page a few times and sometimes I seem to get a command that works? Other times, I get the above. I am not sure what (if anything) I am doing differently between these tries. I have tried clearing my browser cache, selecting a different port and then changing it back to the original selection, etc.
The above error occurs on Debian Testing using Chrome 128.0.6613.119.
The text was updated successfully, but these errors were encountered: