ERROR: 2022/03/02 12:40:56 app.go:511: Unable to start: listen tcp 208.x.x.214:443: bind: address already in use
and also the first time around an SSL request is too long, error.
there may be a few things going on here, but would love some help getting this sorted out.
fqdn will be @ hopefullyread.com 
looking forward to getting a community started where people can blog and enjoy that.
thank you so much 
It looks like port 443 is being used by another program on your machine. Since that’s the SSL port, I’d guess it’s another web server that’s running?
multi domain box -
using vhost file with all the domains in it. apache2 is listening on 80 and 443.
ok its running! i had to copy the certs manually. working for at least 3 months, ha ha… re letsencrypt…
//
ok so now how do i turn on the public reader option, and change the editor to include a subject line??
so excited!
then i rebooted the box, tried to start the server with ./writefreely start
and got this:
which is weird, because i didnt install it as a service…
2022/03/02 18:15:48 Starting WriteFreely 0.13.1…
2022/03/02 18:15:48 Loading config.ini configuration…
2022/03/02 18:15:48 Loading templates…
2022/03/02 18:15:48 Loading pages…
2022/03/02 18:15:48 Loading user pages…
2022/03/02 18:15:48 Loading encryption keys…
2022/03/02 18:15:48 Connecting to mysql database…
2022/03/02 18:15:48 Initializing local timeline…
2022/03/02 18:15:48 Adding www.hopefullyread.com routes (multi-user)…
2022/03/02 18:15:48 Going to serve…
2022/03/02 18:15:48 Serving on https://208.x.x.214:443
2022/03/02 18:15:48 Using manual certificates
2022/03/02 18:15:48 —
2022/03/02 18:15:48 Serving redirects on http://208.x.136.x:80
ERROR: 2022/03/02 18:15:48 app.go:497: Unable to start redirect server: listen tcp 208.97.136.214:80: bind: address already in use
ERROR: 2022/03/02 18:15:48 app.go:511: Unable to start: listen tcp 208.x.136.x:443: bind: address already in use
ok so i moved it off the dedicated server, onto the vps instead… it’s now got a different IP, and is turning on OK, the ssl cert is valid, however i get that PR_ … error (see below writefreely’s run output.)
2022/03/02 20:46:18 Starting WriteFreely 0.13.1…
2022/03/02 20:46:18 Loading config.ini configuration…
2022/03/02 20:46:18 Loading templates…
2022/03/02 20:46:18 Loading pages…
2022/03/02 20:46:18 Loading user pages…
2022/03/02 20:46:18 Loading encryption keys…
2022/03/02 20:46:18 Connecting to mysql database…
2022/03/02 20:46:18 Initializing local timeline…
2022/03/02 20:46:18 Adding www.hopefullyread.com routes (multi-user)…
2022/03/02 20:46:18 Going to serve…
2022/03/02 20:46:18 Serving on https://67.205.x.x:443
2022/03/02 20:46:18 Using manual certificates
2022/03/02 20:46:18 —
2022/03/02 20:46:18 Serving redirects on http://67.205.x.x:80
//
(upon trying to visit the actual website…) from firefox, or seamonkey, I get:
Secure Connection Failed
An error occurred during a connection to hopefullyread.com. PR_END_OF_FILE_ERROR
The page you are trying to view cannot be shown because the authenticity of the received data could not be verified.
Please contact the website owners to inform them of this problem.
and as such, there’s nothing there when I load the domain… confused!
ok we’re live @ read-read.net and hopefullyread.com now.
reverse proxy solved it. thanks @matt for the assistance ! and beautiful software. it’s really wonderful.
how do I get the subject line configurated though?