Krydos

Those look like local includes to me. Have you checked to make sure those included files exist?

The phpmyadmin on your account is working for me. Has the issue resolved itself? https://johnny.heliohost.org:2083/frontend/paper_lantern/sql/PhpMyAdmin.html

I'm glad it's working for you. I agree the cron every minute seems excessive.

Your account is still on Johnny, and that server is very overcrowded. Since it is so overcrowded the load is very high, which means everything will load very slowly or timeout entirely. If you want a faster server with better uptime we recommend switching to Tommy or Ricky.

I'm sorry. For some reason when I was writing that earlier I read it as allow_url_fopen not allow_url_include. We allow a lot of easily hacked software, most notably wordpress, run on our servers, and allowing hackers to include malicious code hosted on another server is a security risk. We can control our own servers pretty well, but allowing users to execute code on some other server that may or may not have any security could be a problem if the remote code is changed by a hacker. Why do you need to include remote code? Why not just upload it to our server and include it locally?

PHP errors are off by default. I had to recompile a few versions of php a while back, and simply forgot to turn errors back on.

Does it work now?

A lot of times that invalid login error on Johnny accounts is caused by the server load being too high. When the load is so high it causes the logins to time out. If you're changing servers anyways an admin can move your account for you if you're a donor, or if you want to move for free an admin can delete your account for you. Just make sure you have everything backed up first. Let us know how you'd like to proceed.

It's currently set to GPCS which is default. The E is a performance hit to list in this directive, and you can access it via the getenv() function anyways if you really need it which most people don't. I think you can just set it via the curl CURLAUTH_GSSNEGOTIATE option. That's a pretty obscure one. This would require compiling curl from source which would undoubtedly break other things. I prefer to keep everything supported through the package manager if at all possible. Cpanel disables this by default for, what I assume is, performance increases. Cpanel disables this by default for, what I assume is, performance increases. This is a security risk. Cookie based sessions are more secure than URL based sessions. I think this is already set. I think this is already set. I'm not sure what this is supposed to mean. The default value is "a=href,area=href,frame=src,input=src,form=fakeentry". This option is related to the URL sessions that I listed above as being a security risk. Overall, I really think that whatever software you're trying to run is going to require a vps if it really needs all of these insecure settings. Luckily for you we provide those.

It's already on. It's already on. The functions that are disabled are going to stay disabled because they are a security risk on a shared hosting plan. It's a security vulnerability to have this on. This would allow criminals to see the vulnerabilities of our php version. Why do you even think you need this on? Max execution time is intentionally kept low to help keep the server load low. If each php process was allowed to run for 5 minutes all of the server memory would be consumed even more easily, and the server would have even more downtime than it already does. Max input time is intentionally kept low to help keep the server load low. It's a terrible idea for uptime to set this much higher than it already is. If this was disabled you wouldn't be able to pass arguments to php on the command line which would make a lot of cron jobs stop working. It would increase performance slightly though so I'm tempted. Why does it matter to you if you can pass arguments on the command line anyways? So you want literally everyone's emails on the entire server to look like they are coming from your account? I don't think you even know what you're asking for. Where did you copy/paste this list from? It's obviously settings that are meant to be run on a vps, not shared hosting. Same as above.

Done. You should now be able to log in and your website should start working within 2 hours.

You would probably need to contact the plugin's author and ask them if they can write a version that doesn't require it to be run on the command line. It doesn't really sound like this Flarum forum is going to be compatible with any shared hosting services since it seems to require ssh and unlimited cron jobs. Have you considered running it on a vps instead? https://www.heliohost.org/vps/

Your account was archived because you haven't logged in for quite a while. We have a limited amount of space on our servers, and occasionally we have to remove the unused accounts to make space for new users. To prevent your account from becoming archived again please remember to log in at https://www.heliohost.org/login/ at least once every 30 days. Unarchiving...

Yeah, that will only work as an internal cron, which is limited to 2 per day.

No, see how https://afwpe.tk/bazaarcron.txt ends with .txt? That's never going to execute because it's a text file not a script. Do you have a script like afwpe.tk/bazaarcron.php or something like that? Also can you post a link to the documentation for whatever plugin or flarum or whatever you're trying to do?

Well, that text file contains a command that you could run on the command line, but it won't work as an external cron because text file aren't executable. Is there a flarum cron path that ends in .php perhaps?

Done. You should now be able to log in and your website should start working within 2 hours.

Your account was archived because you haven't logged in for quite a while. We have a limited amount of space on our servers, and occasionally we have to remove the unused accounts to make space for new users. To prevent your account from becoming archived again please remember to log in at https://www.heliohost.org/login/ at least once every 30 days. Unarchiving...

Suspended.

I honestly haven't even read through the list yet, because it's irrelevant until I know which version of php we're even talking about. I should also mention that if you want to edit your own php.ini or use insecure functions like exec() you won't be able to do that on a shared hosting account like you have, but you can do so on a vps https://www.heliohost.org/vps/

Done. You should now be able to log in and your website should be working again.

Remote access enabled. The remote host can be johnny.heliohost.org, alexger7.heliohost.org, or 65.19.141.67. Any of those three should work.

Which version of php are you using?

We offer 2 types of cron jobs: Internal cron jobs that you can create through cpanel and are limited to 2 per day, and external cron jobs that we can set up for you and can run as often as once every 5 minutes. For an external cron job you need to have your cron script accessible to a web browser such as domain.heliohost.org/cron.php. Just let us know the URL and the frequency if you want an external cron set up.

Your account was archived because you haven't logged in for quite a while. We have a limited amount of space on our servers, and occasionally we have to remove the unused accounts to make space for new users. To prevent your account from becoming archived again please remember to log in at https://www.heliohost.org/login/ at least once every 30 days. Unarchiving...