Only one program can listen on a port at a given time usually. Something’s listening on port 443 (the standard HTTPS port), and when nginx starts up it tries to listen on that port and can’t. You can figure out what’s already listening on that port with commands like lsof or netstat, see here for examples:

https://superuser.com/questions/42843/finding-the-process-that-is-using-a-certain-port-in-linux

Good callout. I’m actually admin on this instance so it wouldn’t apply to me by my reading of the code. Lemmy schedule also doesn’t currently use the scheduled posts Lemmy feature, it tracks it separately. Still good to know though, thanks.

Excited to see the idempotency feature. That will help a lot with double posts from using https://github.com/RikudouSage/LemmySchedule