wolstech

Application pool has been restarted and the 503 error has cleared. Is your domain supposed to be showing a 404 error though? (Lily installed 6 months worth of back updates on Friday night, I'm wondering if something broke...)

Unblocked. It can take up to 10 minutes to be effective.

That can't be restored because the archive was missing. Invite sent.

Username for that is actually gamepug. Unarchived. It may take up to 2 hours to work.

Probably tried too soon. It takes 10-15 minutes to actually unblock, sometimes longer if the server is busy. He tried after 5...

Unarchived. Also, your username is jacobal1, not jacobale.

So, I decided to back up and update the site on Lily...and got it to work. I had to use these settings to make it work, the first two attempts with lower numbers for execution time and upload_max_filesize failed: max_execution_time: 300 memory_limit: 128M post_max_size: 128M upload_max_filesize: 128MThe update for that site was 3.9.5 to 3.9.16.

I wouldn't go that far... The only major issue with Joomla here is that it will not update. It runs fine but the updater will fail and hose the install if you try it.

Considering I manage a few Joomlas myself across 3 servers (none on our cpanel servers, though one is on Lily) and exactly zero will update, I'd blame the product...it's either bad code or bad documentation. Odds are it has some very particular requirements for the updater that most servers don't meet...hostgator is probably one of the few that do. What I would like to know is what that requirement is...

Post max size is already set to 64M. http://krydos.heliohost.org/71/phpinfo.php As I said earlier, it's not the server, their product is just broken. I have a joomla install running outside of here (granted I'm on a WIMP instead of LAMP server) with values much higher than we'd ever consider here, it still won't update...

Failed IMAP logins...you have a misconfigured mail client somewhere and need to check the username and password on every device you have set up to check your email. Unblocked.

Please clear your cache. I'm able to connect to https://edvicon.org without any sort of error. Your certificate is valid for these domains: DNS Name=edvicon.heliohost.org DNS Name=cpanel.edvicon.heliohost.org DNS Name=edvicon.org DNS Name=mail.edvicon.heliohost.org DNS Name=mail.edvicon.org DNS Name=webdisk.edvicon.heliohost.org DNS Name=webmail.edvicon.heliohost.org DNS Name=www.edvicon.heliohost.org DNS Name=www.edvicon.org

That folder is where the system looks for a special file used for domain validation for the cert. Comodo connects to your domain over plain http and expects to find that file there to verify the domain is valid. If you have a redirect of some kind in your document root, the verification won't be able to find the file and you won't get a certificate.

The permissions changes didn't save it looks like...your test.php was still 664 (note the center 6...) even though you tried to change it to 644. As soon as I changed it, the script worked fine: https://www.websoftops.de/test.php

You can put the protocol in the name field after the name, separated with a period. For instance, the _sip record with protocol _tls would become _sip._tls and get entered in the Name/Host field From MS's website (here):

Since he's on Tommy, the server will get him a certificate from Comodo/Sectigo on its own within 24 hours. He needs to do nothing other than use our name servers and ensure he doesn't have a redirect blocking plain HTTP access to the .well-known folder.

Unarchived. It may take up to 2 hours to start working.

We can't troubleshoot or support any site using CloudFlare. Assuming the domain is added to your account, it should just work once you change the name servers back. CF is notorious for causing tons of issues with our service, so it's recommended that you avoid it if possible. The only times I've seen CF be required was when someone needed either the bandwidth support (lots of static content) or advanced DNS functions. 99% of users don't need it.

Unarchived. It may take up to 2 hours to work.

This domain should now be working. Please clear your cache if you still see an error or queued page.

Nope. We intentionally block users from changing this on their own so they don't hog the server resources. Tommy did not have any major outages. Something's broken on your end or with your ISP: http://heliohost.grd.net.pl/monitor/

Unblocked. It was for failed SFTP logins. Please keep in mind that SFTP takes your cPanel username and password only. It does not support email addresses as the username, and also does not support the additional FTP accounts created through cPanel.

It's 3 concurrent connections on Johnny and Ricky, per database user. There's no limit at all on Tommy (though that's subject to change if abused).

That account cannot be restored because the archive is missing. Invite sent.

Unblocked. It can take up to 10 minutes to be effective.