Re: [racket-users] Help narrow down problem using plt-web-server:

2019-01-13 Thread Neil Van Dyke
Regarding the immediate problem, and then a couple things you might see after... * Unless you have a really weird OS, I think the first problem is that another process currently has/had port 443 open on the same network address.  (This might even be from the last run of your same program, as

Re: [racket-users] Help narrow down problem using plt-web-server:

2019-01-11 Thread George Neuner
On 1/10/2019 3:50 PM, Don Green wrote: I suspect that I: (a) may be misusing plt-web-server; or (b) have not actually installed my server-cert.pem properly even though the verification operation indicates a successful installation: openssl verify -CApath /etc/ssl/certs server-cert.pem returns: s

Re: [racket-users] Help narrow down problem using plt-web-server:

2019-01-10 Thread 'John Clements' via users-redirect
Apologies if this is obvious, but have you checked to see whether some other process is already listening on port 443? On a Linux server, it looks to me like you should be able to see what processes are listening on what ports by running sudo netstat -tulpn Also, you don’t mention what the res