Jump to content

Leaderboard

Popular Content

Showing content with the highest reputation since 07/21/2025 in Posts

  1. 1 point
  2. 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
    1 point
  3. 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>
    1 point
  4. 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.
    1 point
  5. Please read: https://wiki.helionet.org/502_Bad_Gateway & https://wiki.helionet.org/504_Gateway_Timeout
    1 point
  6. Krydos can create postgis on it for you. Escalating.
    1 point
  7. Remote access enabled. host=64.62.151.106 port=5432 user=camilogeo_admin dbname=camilogeo_ppgcs password=<set in Plesk>
    1 point
  8. This support request is being escalated to our root admins.
    1 point
  9. Domains added. They can take up to two hours to function.
    1 point
  10. 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.
    1 point
  11. Domain added. it can take up to 2 hours to start working.
    1 point
  12. It is good now thank you so much!!
    1 point
  13. Try the new invite I just sent you.
    1 point
  14. This support request is being escalated to our root admins who have more visibility to dig into this issue some more. In the meantime, could you please provide the PayPal transaction ID, which may help them find the payment quicker?
    1 point
  15. Sorry by mistake I created two post and I tried to delete it but there isn't any option to do that. I will keep that in mind. Thanks for your help
    1 point
  16. An email alias just forwards an email to another email address. You cannot send mail directly from it. If you need to send emails from it, then you would need to create the email as a separate email account instead of an alias.
    1 point
  17. Your account is now being reset. Once the reset completes, you'll receive an email with a link to finish the process and set up a fresh account.
    1 point
  18. You're welcome! 🙂
    1 point
  19. i see that your VPS is using Ubuntu 22, would you like to use Ubuntu 24 instead?
    1 point
  20. I've escalated your request for Wolstech's attention who can set this up for you. 🙂
    1 point
  21. Not sure if I am at the right section of the customer support to report this but just made a donation Transaction ID: 34611125JC9001140 Does my files automatically get back to Morty or do I have to request it? I did receive the notification to increase my donation but it slipped my mind until now. Thanks Duuuhhhh... just received the email about account moving to new server. Guess that solves the above.... Suhorrrrry....
    1 point
  22. Thanks for the additional details. This support request is being escalated to our root admins for their consideration.
    1 point
  23. Account has been reset and a new invite was sent to your email address.
    1 point
  24. I've added that domain to your account for you. Please note that it may take up to 2 hours for the domain change to take effect. If after a full 2 hours it doesn't work on your side, please make sure you clear your web browser cache: https://wiki.helionet.org/Clear_Your_Cache
    1 point
  25. Thank you for the fast reply and help. I will do what is needed, thanks.
    1 point
  26. Glad everything is working for you now. Thanks again for the 5 star review.
    1 point
  27. Yep, it worked. Your account is moving to Tommy. Thanks for the donation. I also noticed that you randomly received a review email. We would be really happy if you could click the link in the email to give us a 5 star review. It will only take you a couple minutes to write a sentence or two about your support request today, and it goes a long way to help us out. We recommend using the link that was emailed to you because 5 star reviews that don’t click the email link pretty much all get deleted. Our volunteers don't get paid in money because we are a non-profit, but our volunteers do get paid in smiles whenever someone lets us know they appreciate our work by giving a 5 star review. Thanks again!
    1 point
  28. They're probably being sent with a fake from header to make them look like you sent them to yourself. Pretty common with spam. Plesk's email system doesn't have a good spam filter, so you're likely going to receive most if not all spam sent to your domain. Decent spam filters will discard these fake From emails as sender spoofing. That said, DKIM, SPF, and DMARC have been set up for the domain bochard.net. We recommend sending a real email (not just the word "test" or a blank email) to https://www.mail-tester.com/ to make sure that everything is set up correctly. If you get less than a 10/10 score please post a link to the full report so we can help you fix any other issues that there may be.
    1 point
  29. An admin will be able to do this for you.
    1 point
  30. You could either contact PayPal support and see what they have to say about it, or you can use this Stripe link to try to pay again https://buy.stripe.com/6oU7sNcs6207fjP1udco009 I understand that the Stripe link says $2 and the dashboard says $1, but the dashboard will be updated to the new pricing soon anyways, and I don't want to create a $1 Stripe link that will only be used once and then deleted in a week or whatever.
    1 point
  31. This support request is being escalated to our root admins who can look into this further for you.
    1 point
  32. Soo as it turns out, on Jonny you can safely place your .env file in the root of your app and the server will automatically prevent it from being served to a client. for this sample project, the path is load_dotenv("/home/dkobrin.helioho.st/flask.dkobrin.helioho.st/MyNewFlaskApp/.env") as an extra layer of safety I am also adding the following to my .htaccess file instructing Apache to deny requests for .env files #hide .env files from http access <FilesMatch ".env"> Order allow,deny Deny from all </FilesMatch>
    1 point
  33. For SPF, use this (leave the name field blank, use this as value): "v=spf1 include:tommy.heliohost.org ~all" For DMARC, enter the name as _dmarc, and use this value: "v=DMARC1; p=quarantine" For DKIM, the record needs to be generated in Plesk under the mail settings as its unique to each user. Turn it on, apply the settings, then click the ? next to the DKIM settings and it will show you the correct records to use.
    1 point
  34. No you can't. Plesk's git cannot be the target of a push. The suggested solution for automatic deployment is what you described (hosted repo on github with a webhook). If there was a way to do this, it would need to be over HTTPS anyway as we don't allow SSH access to the Plesk servers for security reasons.
    1 point
  35. Domain added. it can take up to 2 hours to start working.
    1 point
  36. Domain added. It can take up to 2 hours to work.
    1 point
  37. Account segonist has been reset. When it finishes, you'll receive an email with a link to create a new account. If you need the data from the old account, it will be available at https://heliohost.org/backup/ once the reset is complete.
    1 point
  38. I've added that domain to your account for you. Please note that it may take up to 2 hours for the domain change to take effect. If after a full 2 hours it doesn't work on your side, please make sure you clear your web browser cache: https://wiki.helionet.org/Clear_Your_Cache
    1 point
  39. One of the biggest problems on forums these days is lack of good forum etiquette. What some of the newer users of message boards don't understand is that forums have a very different environment from a chatroom, an instant message conversation, or even an email correspondence. Users of respectable message boards are expected to act maturely. And therefore, to help some of our newer users, I have created this guide to maintaining good forum etiquette. Use spelling and grammar correctly. Always capitalize the first letter in a sentence, even if you only have one to post. Always use periods. Capitalize only when necessary. Remember, all caps means you're yelling. Use commas and punctuation marks. The only excuse you can have for bad spelling or grammar is that you are not a native of an English-speaking country, and even then, you should do your best to learn English.Don't post just to up your post count. In fact, don't even pay attention to your post count. The senior members of a forum aren't respected because they have lots of posts, but because they are good contributors. You should strive to do the same.When you post, make it in-depth. Never just say "I agree" or "Good idea." Describe your idea. Say "I agree because..." or "Good idea. I think..." We want to hear a developed opinion, not just a short statement. Two or three word posts aren't really contributing anything to the forum.Know what you're talking about. Most forums are a community of experts and enthusiasts, and they love to discuss their passions. However, if you go into a topic you don't know much about and say something ignorant, it'll really tick them off. Especially if you stated it with authority.Never ask someone a question you can could easily get answered through a search engine or an encyclopedia. People expect you to find things out on your own instead of getting other members to do it for you. Laziness is frowned upon.Make sure never to turn a topic into back-and-forth conversations on random things. Topics are made for a reason - to discuss something. If you go into a topic and turn it into something completely irrelevant from what it was intended to discuss, you're only ruining it for the users who seriously want to discuss that topic.Don't just go through every topic in a forum posting in each one. Most people will find it hard to believe that you actually have something important to contribute to a topic if you post all over the place.Don't overdramatize unimportant things. There is no need to post a sorry thread if you broke a rule, or make a big deal when something doesn't apply to you. If you made a mistake, no big deal. If you follow these rules, people will forget all about it in a month or so.Don't freak out if no one responds. People have things they need to deal with outside of HelioNet. If you have a question and it has gone several days without being answered, kindly bump the thread up so others may see it.These are just the basics of forum etiquette. You'll learn much more as you post and interact with the community. We won't chastise you for a mistake, but we expect you to do your best to follow this guide. Good luck, and happy foruming © Copyright Helio Networks 2006-2009
    1 point
×
×
  • Create New...