wolstech

Try logging in here: https://tommy.heliohost.org:2083/ As for inactivity, I see a last login of today, so don't worry about getting suspended.

On second thought, I just read that the admin tools are broken. I suspect my change isn't going to work either. Is the new domain showing in cPanel for you? If not, the change failed on my end as well.

I've changed the domain for you, but the new domain is misconfigured or not registered (NXDOMAIN). Please make sure the domain is registered and the nameservers are set to ns1.heliohost.org and ns2.heliohost.org.

It's archived. Escalating to have it restored.

The close action on vb.net doesn't work how you think it does. It leaves the connections open behind the scenes even after you tell it to close them. If it closed them like other languages, you wouldn't be having this issue. PHP actually closes them when you tell it to close them.

You were blocked for failed web page logins. This usually means you password protected a directory, and entered the wrong password too many times when trying to log into it. Unblocked.

The user accounts you create in cPanel are for either email or FTP. FTP logs in using an FTP client, and email is at http://johnny.heliohost.org:2096, please use the full email address as the username. cPanel does not support adding cPanel logins to a single account (you can't give cPanel access to someone else).

I'm assuming you're having trouble viewing the database...you can unpack it and view in a text editor like notepad++ on your PC if you want. Database dumps are usually just (really large) text files.

Unblocked.

Probably a dns issue with your isp. How long has the site existed? DNS can take 24 hours sometimes. Also, have you confirmed that it’s your isp, and not the computer? Try another computer on the same network. A generic error that goes away with a VPN can also be your IP being blocked, but the IP you posted from is not blocked. Are you able to use cPanel through the affected ISP? If not, what is your IP address?

It’s actually suPHP (the apache module that lets php run as the file owner as opposed to the apache user, which is typically nobody) that doesn’t like it. It poses a security risk for files to be writable by the group, so it refuses to run files that aren’t given proper permissions.

Huh. Didn’t show up for me. Perhaps you’d already unblocked it. Anyway, we usually recommend https://heliohost.org/login/ to log in. You won’t be blocked that way if you use the wrong password too many times.

The one you posted from isn't blocked. You can tell us which IP is shown here: https://www.heliohost.org/ip.php so we can figure out which one to unblock?

You can unpack it on the server to speed that up. Upload the archive, then go into cPanel's file manager and extract. It will work as long as its a standard format like tar.gz or zip.

Did you update your SMF database settings? Odds are they changed, especially if your account's username changed between servers.

This is a standard feature on Tommy, so it's already enabled. Your website is coded to redirect to a non-secure version of your page though, so you'll need to fix your code to not do this.

Fixed.

Change them to 644 and they’ll work.

Digging into that a bit more, that is actually rather impressive...it can’t do dynamic content (at least without custom code) but for everything else, it seems like a good alternative.

Side by side should work just fine if Krydos says ok. No downtime needed, or risk of breaking the wiki beyond repair. If the new install gets botched, just start again. @miwilc: If someone else is willing to do this major undertaking for us, it should be welcomed. I can safely say that it is unlikely that it will get done in reasonable time by any existing admins.

Yeah bad htaccess files will do that. First step for any 500 error is generally to rename .htaccess if it exists so its ignored. File permissions come second, then after that it gets a little more difficult to solve (python files with bad shebang lines, etc.)

Check the file permissions. They need to be 644. Odds are you have them set to 664 (Apache does not like php files being writable by the group) since the SFTP upload settings we use default to 664. Our servers have display_errors enabled by default, so if it was the script, php would spit out errors instead of a 500.

This support request is being escalated to our root admin.

That app produces static websites (I.e. html files). There is no control panel or anything. The upside is that the site produced is fast and effectively hack proof. Downside is you have to edit manually, write your own code if you want to do anything outside what the app offers to build, etc. Not really a good solution for most, but almost better than the bloated malware-fest that is WP. I personally built my own crude CMS since I didn’t like what was on offer, but that’s overkill for most. We have lots of users with joomla, they seem to be quite happy, and though it can face the same issues as WP if misconfigured or left unupdated, malware is less prevalent with that system it seems.

Escalating so the contents of your account can be deleted for you.