Jump to content

wolstech

Chief Risk Officer
  • Posts

    18,514
  • Joined

  • Last visited

  • Days Won

    718

wolstech last won the day on December 10

wolstech had the most liked content!

About wolstech

  • Birthday May 17

Contact Methods

  • Website URL
    https://www.raxsoft.com

Profile Information

  • Gender
    Male
  • Location
    Pennsylvania

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

wolstech's Achievements

Grand Master

Grand Master (14/14)

  • Well Followed Rare
  • Reacting Well Rare
  • Conversation Starter Rare
  • Dedicated Rare
  • Very Popular Rare

Recent Badges

1.5k

Reputation

  1. The .well-known folder is a weird folder, I've run into a few different things that behave strangely in there. You'll need to remove the below section (or at least add a second condition that allows access to the acme-challenge folder and anything inside) if you want Lets Encrypt SSL certificates to work properly. # Block directory browsing in .well-known paths RewriteCond %{REQUEST_URI} ^/\.well-known(/openpgpkey(/hu)?)?/?$ RewriteRule ^ - [F,L] Plesk creates things in /.well-known/acme-challenge to verify the domain, so you cannot restrict access to that folder. Some other services you might want to use also need access to .well-known too, so we generally recommend not restricting .well-known at all. Also, be aware the Options line in .htaccess doesn't behave very well on Plesk, so that line may or may not do what you expect. Usually if they're not supported, they're either ignored entirely (why you had directory listings despite Options -Indexes being in there), or will cause a 500 error (which will have a line in the logs saying "Options directive not allowed here").
  2. The supported way to turn off directory listings on our service is to put an empty index.html file in the folder to hide the listing.
  3. Looks like it might be working for me? I get this instead of a directory listing, which I assume is from your app:
  4. Morty's /tmp was full again. Another user's Node app was malfunctioning (or more correctly, missing, the user deleted the files without disabling node, causing Passenger to sit there and fill up /tmp with error logs until the server broke). The broken node app has been disabled, the /tmp folder was emptied, and Morty is now working again.
  5. I see a 404 error at that link. Does that page exist?
  6. Domains added again. They can take up to 2 hours to function.
  7. This is probably a Krydos issue...escalating.
  8. You can move to Morty instead to avoid the inactivity requirement if you want. That server replaces the activity requirement with a $1/month fee instead. Otherwise, as above, this requirement has been the same for 15+ years. Not sure where you read the incorrect information you have, but the instructions in Unknown025's post are correct. The only thing that avoids suspension for inactivity aside from paying for Morty is to log in at https://heliohost.org/login/ once every 30 days. Email use, FTP, web traffic etc. does not count as activity. Also, for the support and reminder emails not working, it's because you unsubscribed. If you unsubscribe from any of our emails, you will receive NO emails from us, with the sole exception of Terms of Service update notices (which are required for legal reasons). That means you can't use email support and won't receive inactivity reminders. Do you want me to resubscribe you so you can use support and you're alerted prior to inactivity suspension next time?
  9. We also need the name of the database user. Once you provide that, I can escalate this to have Krydos enable it for you.
  10. Please check your PMs for information regarding your Lily account.
  11. There's no indication on our side that you ever attempted to sign up for anything, let alone finished and actually had an account created. What were you trying to sign up for, a Johnny account?
  12. The DNS settings you specified are incorrect. Correct DNS settings are either two NS records pointed to ns1.heliohost.org and ns2.heliohost.org, or A and AAAA records (for IPv4 and IPv6, respectively) pointed to the IP addresses shown in Plesk (which are different from those used for ns1 and ns2). Domain added. Once you correct the DNS records, the domain can take up to 2 hours to function.
  13. The contents of ~/httpdocs (for domain yanshuwang.heliohost.us) have been discarded and your account has been unsuspended. The account can take up to 2 hours to work. If you need a copy of the data, it's available via https://heliohost.org/backup/
  14. Deleted. Thank you for using HelioHost.
×
×
  • Create New...