Chillidog Hosting, PHP and upload issues

[ercross (Edward Cross)]

I’ve been working on improving my website which is using the cms for a blog. The site seems to be working fine, but I’ve had it happen a three or four times now, but not every time. When I publish updates, it breaks the php and the blog pages don’t work.

I’ve tried then republishing and that didn’t fix it. So I went to my cPanel on my Chillidog hosted site and even though it said PHP was using version 8.4, I reset it to do so and this fixes it.

Any ideas of what might cause this? Has anyone else experienced this?

[PMUK (Paul Moore)]

Might not apply to you but I had a problem with PhP and Chillidog. I thought I was on Php 8.4 but some of my domains were on PhP 7.1. SO if you have updated to PhP 8.4 and dont have a problem now maybe like me you were not on PhP 8.2 or above?

[differentdan (Daniel)]

Hi @ercross

Going out on a limb here, because neither RapidWeaver Classic nor Elements has the ability to alter the PHP version on your web hosting account, but if you have included a .htaccess file in your file list in RapidWeaver, and you have a PHP directive in that .htaccess file that sets it to a different version than your account’s default, I think that would be the only possible way that RapidWeaver would be able to make that kind of change.

So, do you have an .htaccess file in your RapidWeaver project file, and if yes does it contain any PHP directive that sets the site’s PHP version?

[ercross (Edward Cross)]

Hi Dan,

I do have a htaccess file, but no php directives in it. See below:

Enable URL rewriting (required for pretty URLs, redirects, etc)

<IfModule mod_rewrite.c>
  RewriteEngine On
</IfModule>

Security Headers

<IfModule mod_headers.c>
  Header always set X-Content-Type-Options "nosniff"
  Header always set X-Frame-Options "SAMEORIGIN"
  Header always set Referrer-Policy "strict-origin-when-cross-origin"
  Header always set Permissions-Policy "geolocation=(), camera=(), microphone=()"
  Header always set Strict-Transport-Security "max-age=63072000; includeSubDomains; preload"
</IfModule>

Enable Gzip compression

<IfModule mod_deflate.c>
  AddOutputFilterByType DEFLATE text/plain text/html text/xml text/css application/javascript application/json
</IfModule>

Disable directory listing

Options -Indexes

[differentdan (Daniel)]

Ok nothing in that .htaccess file is setting the PHP version for your site, so then there’s nothing in RapidWeaver Elements (or Classic), that would break your PHP version after publishing.

If you happen to run into this again, add a page called phpinfo.php in your hosting account and add the below code to it:

<?php
phpinfo();
?>

Then visit your site (https://example.com/phpinfo.php) and see what PHP version it’s reporting. If it’s changing from PHP 8.4 to something else, that’s something you’d want to investigate with your web host.

[ercross (Edward Cross)]

This has gone from bad to worse. I decided to republish the site, so I deleted all the files through cPanel and made sure the trash was empty. I then did a republish all, but it keeps failing at different files about half way through.. It’s trying to upload >4800 files. Below is the error that I got back. I had the connection speed at 6 - Lightening which is what I always use. So I tried it on 4 - Fast and it still failed.

[Fuellemann (Jan Fuellemann)]

Hi, this happened to me as well. I needed to go to 1 to have everything uploaded.

[differentdan (Daniel)]

@ercross

This has gone from bad to worse.

You might want to check out Elements Hosting Updates - 1st edition then.

But I would suggest switching over to SFTP instead of FTP. SFTP is more stable, and your current web host offers it.

[ercross (Edward Cross)]

I restart my router, rebooted the computer and tried again, but it failed. So, I tried on the 1 - Slowest setting and the site did finally upload.

I have now switched to using the SFTP and will see how that goes.

[differentdan (Daniel)]

SFTP is generally more stable, so try slowly moving the connections back up and testing.

With SFTP you can usually get the full 6 connections going with no problem.

[ercross (Edward Cross)]

Unfortunately, SFTP keeps failing even sooner on the slowest speed. I added the :23261 port at the end of the hostname and it pass if I hit the Test button, but it is failing when I try to publish.

So for now I switched it back to FTP until I can contact Chillidog.

Also, I added the phpinfo.php and sure enough, after I do an change and publish, it is reverting back to 7.4.33, so I have to contact Chillidog and see why it’s reverting back.

[differentdan (Daniel)]

Yeah they would really need to look into that then.

Let us know how you get on, or if there’s anything else we can help with.

[PMUK (Paul Moore)]

what’s your setting for SFTP? For chilidog using this setting needs a server setting of “nacho.chillidoghosting.com:23261”

[dan]

@ercross have you tried emailing Chillidog support for help on this one?

I’m cc’ing @barchard and @LaPan as they should be able to look at the logs on their end and find out why the server keeps dropping the connection

[ercross (Edward Cross)]

Hi Dan,

Evidently, when you specify the PHP version on the server, it writes code to the .htaccess file. I was uploading an .htaccess file when I published which didn’t have it.

Still working on the SFTP issue.

[ercross (Edward Cross)]

Hi Paul,

I am using “wtbc.net:23261”

[PMUK (Paul Moore)]

If on chillidog try what I have put as this is what @barchard told me to use as I was having problems publishing and spending time with @differentdan on a 1:1. Give it a go it can’t cause harm. TIA

[differentdan (Daniel)]

Yeah this is what I was hinting at in my initial reply, whether the .htaccess file was either overwriting, or getting overwritten, somehow.

So in this case seems you had an .htaccess file included in your Elements page list that was overwriting the one on the server.

Just a side note, I’m not a fan of including an .htaccess file in RapidWeaver’s page list. That should be explicitly managed on the server because of things just like this.

Regarding the Server/Host setting, try using your server’s IP address followed by the port. For example:

123.45.678.910:23261

That’s usually less problematic. You can see your server’s IP address in your CDG cPanel >> Right hand side.

If you continue to have troubles with it best to ask the guys at Chillidog to take a look at the server logs to see what’s up.

Let us know how it goes.

[ercross (Edward Cross)]

I tried with the ip address of the server. The Test but says it makes a connection, but it fails right away when trying to publish a minor change to one page.

I’ve got a ticket in with Chillidog so hopefully they will be able to get to the bottom of the SFTP issue.

[PMUK (Paul Moore)]

Ok Greg and Brian have been tagged so they will get back to get to you, with time difference in UK I normally have communications around 1800. Good luck!