You can check that port really available. Something like

telnet  host port

and type there anything. If port is available you will get some "garbage" on the screen from vServer.

Probably you made more changes to vServer ini like ACCESSCONTROLLIST - if so, please send me that ini, so I can be more specific.

sorry but my mac/terminal does not have telnet..., ping does not work...

but I can run a webapp using port 9000 (have opened up for that), no prob... but Vserver can not be reached...

You may use ssh instead of telnet - no problem. You need just some tool to check port (not only host) availability.
Mac's "Network utility" could be helpful as well...

Anyway, it is a question for Amazon mainly - not Valentina.

The only thing you should understand - if you send anything (any garbage) to vServer, then vServer disconnects your connection sending error packet before, and you will see this in the output. This fact can be used to check - is the port available + is there vServer, listening for connections.

Hi, I've tried many times now... but opening 15432 does not do it.. and looking on the server from VStudio internaly on ther server reports connection of 53XXX og 62XXX and such....

Could someone at paradigma please try to make VServer run on an free tier EC2 Amazon virtual server. And tell us what ports to open... it does not work with adding it to the windows firewall ...please HELP.

Please check again Amazon firewall settings. If you have a few AWS instances then probably you were tuning another instance (wrongfully)? Please send me a screenshot of firewall settings (that one with opened vServer's port) and screenshot of instance properties (to make sure that tuned firewall is assigned to expected AWS instance).

One more thing:

Please check vServer ini to be:
1. VERBOSELEVEL = 3 (just for now to see max vServer events in the log);
2. PORT_NOTIFICATION = 0 (probably it is the reason - let's check it).

Also, please check vServer logs - is there any records?
I hope you are connecting from vStudio using "connect to" dialog - not waiting for Bonjour (it would not work since there are different networks for vClient and vServer).

Helge - have you tried Sergey's suggestions?

Hi , problem found... I had to set the amazon security group to allow port 15431-15436.... if I leave out 15436 I can not connect... strange ??? since I'm using 15432 as connection port (standard).

Now it works. but why 15436 ?

It is default PORT_NOTIFICATION (see vServer ini). This port is used to get asynchronous notifications from vServer.

OK, that explains it. Thanks.

So exists 2 choices:

1) disable notifications port in the INI file of Vserver
2) open ports you going to use.

You can see list of all ports, which VServer can use in its INI file.
Exists yet for REST, SQLite, ...

Now I've come further. But now I run into error msg on my windows.... on mac it runs fine...

I have copied according to the deployment of xojo windows...