When I do so, it appears that mod_wsgi-express does in fact start an instance of the browser - but it's on port 8000.
The command output looks like this:
roundup@admin-00:~/frodo$ mod_wsgi-express start-server --https-port 8080 2>&1 | tee mod_wsgi-express.out
Server Root : /tmp/mod_wsgi-localhost:8000:2000
Server Conf : /tmp/mod_wsgi-localhost:8000:2000/httpd.conf
Error Log File : /tmp/mod_wsgi-localhost:8000:2000/error_log (warn)
Operating Mode : daemon
Request Capacity : 5 (1 process * 5 threads)
Request Timeout : 60 (seconds)
Startup Timeout : 15 (seconds)
Queue Backlog : 100 (connections)
Queue Timeout : 45 (seconds)
Server Capacity : 20 (event/worker), 20 (prefork)
Server Backlog : 500 (connections)
Locale Setting : en_US.UTF-8
And nmap shows that port 8000 is in use, but port 8080 is not.
I suspect I have something wrong in the command statement, but I don't know what it is.
The port is not blocked by a firewall.
This message contains confidential information. If you are not the intended recipient, notify the sender immediately and delete this e-mail from your system. You should always check e-mail for viruses. Sender does not accept liability for any viruses that may
be inadvertently transmitted.