Jump to content

wolstech

Chief Risk Officer
  • Posts

    16,153
  • Joined

  • Last visited

  • Days Won

    566

wolstech last won the day on March 23

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

Veteran

Veteran (13/14)

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

Recent Badges

1.2k

Reputation

  1. Name servers are ns1.heliohost.org and ns2.heliohost.org.
  2. Removed. Thank you for doing your part to help keep our servers fast
  3. Reverse DNS should have zero impact on the availability of a website hosted on the box. All reverse DNS does is map an IP to a name (as opposed to a name to an IP). It's basically just an entry in a backwards phone book...you have a number and want to know the domain it belongs to. It's mostly used for things like mail spam prevention. The fact the site is working for me only over plain HTTP makes me think either the site is not configured to accept HTTPS. I got a security warning earlier, but now it just automatically redirects to plain HTTP. Also, a browser configured to only allow HTTPS connections (I know Firefox has this as an option) would see your site as unacceptable... You may want to check the configuration for HTTPS and also renew the certificate if needed. EDIT: After clearing cache, I now just get connection refused over HTTPS, so yeah, it's not responding on 443. Either apache/nginx misconfigured or port possibly blocked in firewall?
  4. I spoke with Krydos on this, he confirmed this issue does not look to be on our end, but rather an issue with DNS propagation of the name server settings from in.eu.org. He was able to show that some servers around the world are reporting cloudns as the DNS provider, which is obviously incorrect. You'll need to contact the admins who handle in.eu.org for assistance with this issue (note that in.eu.org has a different admin from eu.org).
  5. Are you using Cloudflare for your domain? If so, turn off strict SSL if it's enabled. The site is working for me when accessed via its service URL: http://vps36.heliohost.us/ and https://vps36.heliohost.us/ (it lets me ignore the cert warning then redirects to plain HTTP...).
  6. I'll let Krydos take a look at this as I don't see anything wrong on our end. Zone files look fine, check fine, and resolve when queried directly. He's the expert on these name servers though. I did correct missing A records for your subdomains on Cody (my fault as when I restored this for you I didn't know the DNS servers don't actually talk to each other...), but that didn't resolve the fact the root domain itself still won't resolve. As for this morning (on a different computer), I get this. The major DNS providers just return nothing at all for your domain. At work last week they returned an NXDOMAIN. C:\Users\Owner>nslookup sgnetworks.in.eu.org ns1.heliohost.org Server: UnKnown Address: 2001:470:1:1ee::3 Name: sgnetworks.in.eu.org Address: 65.19.141.67 C:\Users\Owner>nslookup sgnetworks.in.eu.org ns2.heliohost.org Server: UnKnown Address: 2001:470:1:1ee::2 Name: sgnetworks.in.eu.org Address: 65.19.141.67 C:\Users\Owner>nslookup sgnetworks.in.eu.org 1.1.1.1 Server: one.one.one.one Address: 1.1.1.1 Name: sgnetworks.in.eu.org C:\Users\Owner>nslookup sgnetworks.in.eu.org 8.8.8.8 Server: dns.google Address: 8.8.8.8 Name: sgnetworks.in.eu.org
  7. The server still has nginx running even if apache is turned off. Nginx can support PHP without Apache.
  8. To use CF, you just add the domain in CF, it will try to copy the needed records. If that succeeds, you can just change the name servers at your registrar to what they give you and it will work. If you want to configure manually in cloudflare, you just set the A and AAAA records for the base domain to the IPs shown in Plesk, and create a CNAME for www that’s pointed to your domain. If you need email to work, there’s additional records needed as well (an MX, and 2 TXT records for SPF and DKIM).
  9. Unsuspended. It may take a few minutes to work. To clarify the policy for others who may read this, users are allowed one Plesk account total , not one account per server. Users cannot have an account on both Plesk servers at the same time. Also, the multiple account policy does not apply to VPSes.
  10. You're suspended for having more than one account. Which account do you want to keep?
  11. Domain added. It may take up to 2 hours to work. For the certificate, uncheck the wildcard box and try again. The wildcard option is not supported.
  12. In fairness other users, we were unable to waive the registration wait or the “lottery” required to get an account for free. When I got my account back as a regular user, I had to get up at 3 AM for it. This is a known pain point for users in certain areas of the world (eastern half of Europe and west Asia notably). There have been discussions about potential solutions such as offering a second round of registrations at times that aren’t in the middle of the night for these regions, but nothing has been implemented to date. If you do not wish to or unable to wait and hope you can get a free account, you can donate $1 anytime and receive a Tommy invite within minutes that works whenever. https://heliohost.org/tommy/ (If there’s a specific reason you want to be on Johnny, we can also offer you a Johnny invite in place of Tommy for the donation).
  13. This user is no longer with heliohost (which is kind of sad, because he was an awesome moderator). You can find the same info here for Johnny: https://krydos2.heliohost.org/pyinfo/info3.10.py https://krydos2.heliohost.org/pyinfo/info3.6.py https://krydos2.heliohost.org/pyinfo/info2.7.py For Tommy, remove the 2 after krydos.
×
×
  • Create New...