[Solved] Over 3 min for loading my index page

[gioller]

I always waiting over 3 mins before can see my web page. If this is a normal loading time and does not depend on technical problems, you can cancel my account.

 

[wolstech]

You're on the wrong server if you're trying to run a production-grade website. Tommy is the server for production websites that need pages that always load and load quickly (in seconds).

 

The other two servers are significantly slower. Ricky can be very slow at times as you're seeing due to age (12 year old server) and crowding, and Johnny's uptime is terrible since he's an overloaded test server (not for production use).

 

Getting a free account on Tommy is nearly impossible due to demand and we generally require donations to get an account outside the free signup window, but if you want, I'd be happy to move your account and offer you a trial for 2 - 3 days before you donate to be sure he meets your needs. If you're not happy, we'll just cancel your account after that time instead. Would you like to try?

[gioller]

Yes,ok.Thanks for this offer.

[wolstech]

Alright, I've moved you to Tommy. Your trial is good until Wednesday Jan 16, 2019. Please let us know what you think by then. If you decide to donate, please do so and post the transaction ID here. If you decide not to, your account will be suspended at the end of your trial.

 

If you see a 404 error or suspended/queued page, please clear your browser cache and flush your OS DNS resolver cache.

[gioller]

I try now, and load time looks good. But I have this problems now:
- I can't enter to  SFTP. I try with FileZilla and WinSCP but connection goes to time out.

- in my test page I see Strict and Warning messages that are not good for a production site. But I can't modify php.ini to not display them

- in the test page there is a link to a page that results in error 404. It can not be a cache problem because it has never been loaded

[Krydos]

- I can't enter to SFTP. I try with FileZilla and WinSCP but connection goes to time out.

You're most likely trying to connect to Ricky's IP or port still. Try these settings:

SFTP host: tommy.heliohost.org
SFTP port: 1342
SFTP protocol: SFTP
SFTP logon type: Normal
SFTP Username: gioller
SFTP password: <same as cpanel>

- in my test page I see Strict and Warning messages that are not good for a production site. But I can't modify php.ini to not display them

You don't need to edit php.ini to turn off errors. The best way to get rid of the errors is to edit your code so there are no longer any errors to report, but if you'd rather just hide them put

error_reporting(0);

at the top of your script.

 

- in the test page there is a link to a page that results in error 404. It can not be a cache problem because it has never been loaded

What is the url?

[gioller]

1, yes I change from ricky to tommy, but in the cpanel port for tommy is showed as 1312,
2. thanks. Plus I have correct errors
3. link is http://pangya.heliohost.org/emoticons/emot_box.php
 

[wolstech]

1, yes I change from ricky to tommy, but in the cpanel port for tommy is showed as 1312,

2. thanks. Plus I have correct errors

3. link is http://pangya.heliohost.org/emoticons/emot_box.php

Tommy port is definitely 1342. If it says 1312, it's a typo on our part. We also support vanilla unencrypted ("plain") FTP on port 21. Some users have better experiences using that instead. Just be aware it's insecure.

 

As for the 404 error, there's a ton of problems. First, your .htaccess file in public_html is preventing that from being accessible. Second, you forgot to change the file permissions. I've renamed the .htaccess in public_html to disable it and fixed the permissions on the emoticons folder and emot_box.php for you.

 

You need to change your PHP files to 644, and all folders inside of public_html need to be 755. Once you do that, your scripts should work. I would also recommend figuring out what's wrong with that .htaccess file.

[gioller]

For the FTP changing port to 1342 has solved.

I made the change on permissions and now work.

 

For the htaccess I do not know what does not work. If I remove it, everything works but PHP 5.6.38 is loaded on the server. But from cpanel I changed it in 7.2.

If I use the 7.2 and in htaccess I do not insert the code related to joomla the site is not accessible (all pages show internal error).

However, the problem was related to file permissions, I think.

Edited January 14, 2019 by gioller

[wolstech]

 

For the htaccess I do not know what does not work. If I remove it, everything works but PHP 5.6.38 is loaded on the server. But from cpanel I changed it in 7.2.

If I use the 7.2 and in htaccess I do not insert the code related to joomla the site is not accessible (all pages show internal error).

That's possible. When we troubleshoot internal server errors, the first thing we do is rename .htaccess files and check the file permissions. I did both at once and didn't check the two causes individually, so it's possible the htaccess file is not an issue at all. If it works with the Joomla code in it, then you're good. 

[gioller]

Thanks for support. I have made a donation. This is the ID of transaction via paypal: 19J91702T60952151

[wolstech]

Your trial is now a normal Tommy account and will no longer expire.

 

Please be sure to log into cPanel via https://tommy.heliohost.org:2083/ (with nothing after the slash) or https://heliohost.org/login/ at least once per month to avoid inactivity suspensions. As long as you do this, you can keep the account as long as you wish. If you forget to sign in, you can renew your account from the inactivity page, or let us know and we can renew it for you.

 

Thank you for the donation