Beiträge von aronianh

Zitat von Paul

Yes, there will definitely be some kind of limit. There is no other way in such shared environments. The only question is whether these limits are communicated transparently or not. Probably not in this case. But given the prices, it's quite understandable.

It's a pretty tough nut to crack. I ran some tests and the IOPS is good on netcup (even better than on the provider where I do not have the same issues), but for some reason I am encountering the exact situation OP is describing. Unfortunately it is not worth it for me to investigate further, so I will leave it at that.

Having a similar situation with RS 8000 G9. The conclusion is that netcup does limit IOPS?

Zitat von aronianh

I got it working (ie can accept connections on 8001) by following the commands under `You can also flush your entire iptables setup with the following:`.

After reboot it seems to reset the iptables settings and again cannot receive connections on 8001. So if anyone can offer advice on this it would be greatly appreciated.

Using Ubuntu 18.

Zitat von m_ueberall

Are you sure the service itself is up and running (that is, netstat -tulpen|grep :8001 lists an open port)?

If it is, it may be related to service-specific access rules. In that case, I'd suggest stopping your service and try to use netcat/nc in order to ensure that port 8001 can be contacted remotely (see Netcat/nc command with examples). This should allow you to rule out any non-service-related problems first.

Yes, it is listening.

I got it working (ie can accept connections on 8001) by following the commands under `You can also flush your entire iptables setup with the following:`.

The software I am trying to run needs to be able to receive connections on port 8001 but it cannot. Config locally looks good:

ufw status output

iptables --table nat --list

How can I debug this? Thanks