Standalone quits on webserver

Hi,

I can build my app for Mac, run it in terminal and access website via browser.

Building for linux 64-bit, running it in Terminal, I see my debug message from app.open, but that I come back to terminal prompt.
Like something failed, but no error message.

What could that be?

[quote][centos@ip-172-31-17-30 HTTPDocs]$ ./test --port=9000
App.Open
[centos@ip-172-31-17-30 HTTPDocs]$
[/quote]

No error message. But echo $? shows 255 as error code.

I see in debug mode, there may be an error “ServerSocket could not be started” printed to console.
But not in deployment. <https://xojo.com/issue/50466>

seems to run although I feed it may be local host only.

[quote][centos@ip-172-31-17-30 ~]$ curl http://127.0.0.1:9000
{“code”:“ResourceNotFound”,“message”:"/ does not exist"}[/quote]

is that a normal response from a Xojo web app?

Try

Or try to daemonise the app ?

A value of zero gives you the first nic… eth0.

with port 9001 it does start indeed, with or without the background option.

The problem seems now to be that some firewall still blocks.

[quote=360722:@Christian Schmitz]with port 9001 it does start indeed, with or without the background option.
The problem seems now to be that some firewall still blocks.[/quote]

Try disabling SELinux?
Sometimes that block applications from accessing ports.

Details

Or port 9000 is in use and the web app can’t bind to it.

I fixed it by opening the centos firewall.

still I hope Xojo can print message if socket can’t be opened and give hint where the problem may be.