search

beakerbrowser / dathttpd

Replaced by Homebase! See https://github.com/beakerbrowser/homebase.
MIT License
280 stars 35 forks source link

Error: listen EADDRINUSE :::8089 #10

Closed sull closed 7 years ago

sull commented 7 years ago

I don't have port 8089 in my .dathttpd.yml (removed metric entry). I noticed it was hardcoded in lib/metric.js. Regardless, my server is not showing 8089 being used by any process. But if I try to start dathttpd, this is the error I keep getting.

taravancil commented 7 years ago

You're right, the metrics server runs by default on port 8089.

Strange that 8089 doesn't appear to be used though. Maybe you've already tried this, but does this still happen if you stop dathttpd and then start it again?

pfrazee commented 7 years ago

Try setting it to a different port and see what happens. Not sure what could be going on here.

sull commented 7 years ago

I'm setting up a new dedicated server (was just initial test before). I'll post my results.

sull commented 7 years ago

Seems to be working properly on new test server.

Testing with your dat'ified blogs:

https://paulfrazee.no.center https://taravancil.no.center

pfrazee commented 7 years ago

👍 good deal! closing for now

sull commented 7 years ago

This test was using wildcard dns. I noticed the letsencrypt integration did not create unique cert for each test subdomain that I had added. I'll look into letsencrypt current support for wildcard certs. Anything worth discussing on the dathttpd side?

Also, is a .well-known supposed to get created? Not seeing it.

pfrazee commented 7 years ago

It didnt create unique certs? That's a sign of a bug, it should definitely support that right now.

The .well-known is served dynamically on the https server.