Leaderboard

What is the username of your coworker?

TL;DR: How should one follow through with additional CSRs created via Plesk when submitting them to CAs? Webroot seems to be unavailable due to nginx blocking access to /.well-known/acme-challenge. Hey! I apologize if this question has been asked before in the forums, but I could not find a proper answer to what I've been looking for after a day or two of messing around with things. I would like to know what would be the correct way to get a CSR emitted via Plesk to be signed from a CA like Let's Encrypt. After looking through the wiki, I found out that we're using SSL It! to automatically generate SSL certificates for our websites, and that's great! But I'd like to issue a second certificate, separate from the one used by the website (for security reasons) for me to use on TLS authorization during connections in my applications. They currently run in my own computer (since I don't own a VPS yet), and it would be nice to be able to validate that I'm indeed connecting to the right server, which would be impossible with a self-signed certificate. Thing is, with the old cPanel (after verifying in Ashoat's old GitHub heliohost-wiki repo - Link), it was possible to create a /.well-known/acme-challenge/<requested-file> path that was publicly accessible - and therefore, would pass the webroot challenge of ACME clients like certbot. After the move to Plesk, and I assume with the advent of other changes, nginx has been set to forbid access to the acme-challenge path and throw a 403, and I'm unaware if there is a way to properly allow access to files within that path. I appreciate the time you guys put into reading this wall of text (I've put a little TL;DR up there if it ends up being a lot..), and I'm welcome to both suggestions and opinions as to what I should be doing, and most importantly: should NOT be doing 😄 - Fallbork

Remote access was already enabled for that database, and the remote access was transferred to Morty when your account was moved. The problem is you're using the host "morty.heliohost.org" and you should be using the host "65.19.154.94". Thanks for translating it to English for me. host=65.19.154.94 port=5432 user=camilogeo_admin dbname=camilogeo_gis password=<set in Plesk>

Changes to the state of a domain take up to 2 hours to take effect. It's not instant. The domain is already working for me though, so if you're still seeing a 404 error, please clear your cache.

Please read: https://wiki.helionet.org/502_Bad_Gateway & https://wiki.helionet.org/504_Gateway_Timeout

Krydos can create postgis on it for you. Escalating.

Remote access enabled. host=64.62.151.106 port=5432 user=camilogeo_admin dbname=camilogeo_ppgcs password=<set in Plesk>

This support request is being escalated to our root admins.

Domains added. They can take up to two hours to function.

The _ character is not allowed in a domain name. Are you ok with hyphens? And the answer your other question, you're limited to one node application per domain. Please keep in mind that running more than one on your account might subject you to load suspension anyway. Node is very heavy on memory usage.