On Monday, November 13, 2017 at 11:27:39 PM UTC-8, Dave S wrote: > > [..] > Finally, I stopped Rocket, did a --standalone update, and got my cert. > Restarted Rocket, and got connection refused. Hmmm. > [...] > 1. Rocket did not give any useful information about the problem, or even > admit that there was a problem. > > Still struggling with Rocket, which I need for some WinInet clients [*]. Currently I can run nginx on either 443 or 9090, with curl and libcurl talking happily to it (and WinInet thinks it is happy, because it leaves too fast). Put Rocket on either of those ports (with python web2pypy -a -i 0.0.0.0 -p 9090), and the connection refused results turn up, with no clue from Rocket as to what is happening. netstat -anp shows a python process listening on the port.
Any suggestions? * discussed in other thread /dps -- Resources: - http://web2py.com - http://web2py.com/book (Documentation) - http://github.com/web2py/web2py (Source code) - https://code.google.com/p/web2py/issues/list (Report Issues) --- You received this message because you are subscribed to the Google Groups "web2py-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
