Git deploy issue

[OhFarts]

Ahoy

I'm using Git Version Control since a few days. I was able to setup everything as needed and used a few times the "Deploy HEAD commit". Everything was working fine until today ...

I'm still able to pull data from Github to my cPanel "dev" folder but then I'm not able to deploy anymore. The button is disabled and the well known error message below appear

The system cannot deploy

For deployment, ensure that your repository meets the following requirements:

1. A valid .cpanel.yml file exists. Pour en savoir plus, lisez notre documentation.
2. No uncommitted changes exist on the checked-out branch.

Here's my .cpanel.yml

---
deployment:
  tasks:
    - export DEPLOYPATH=/home/cpxxx/xxx.com/www/
    - /bin/cp -R /home/cpxxx/dev/cron $DEPLOYPATH
    - /bin/cp -R /home/cpxxx/dev/css $DEPLOYPATH
    - /bin/cp -R /home/cpxxx/dev/font $DEPLOYPATH
    - /bin/cp -R /home/cpxxx/dev/img $DEPLOYPATH
    - /bin/cp -R /home/cpxxx/dev/inc $DEPLOYPATH
    - /bin/cp -R /home/cpxxx/dev/js $DEPLOYPATH
    - /bin/cp -R /home/cpxxx/dev/owl-carousel $DEPLOYPATH
    - /bin/cp /home/cpxxx/dev/index.php $DEPLOYPATH
    - /bin/cp /home/cpxxx/dev/login.php $DEPLOYPATH
    - /bin/cp /home/cpxxx/dev/.htaccess $DEPLOYPATH

Nothing changed since my last deployment. I'm the only "developper" using it.

Unfortunately, the hosting company is not even able to solve all the problems I have since I moved to cPanel (can't enable DNSSEC, jetBackup not working, timeout issues when using HTTPS) ...

 

[cPRex]

Hey there! I'm actually wondering if these are all related due to an underlying issue. Since these all deal with security, could there be an issue with the server's clock or time settings causing a problem? If the clock is off, that would cause issues with JetBackup and https connections, so that could also cause problems with Git. Can you check that?

 

[OhFarts]

Thanks for your help cPRex

Sorry I think I didn't put enough details.

HTTPS is working but really slow (almost 30s to load a page). Issues with jetBackup are host side, I guess they have trouble setting this up
I checked the clock anyway and it's correct : Tue Dec 8 16:27:15 CET 2020

 

[cPRex]

Well, it was a good thought!

The slow https issues could be due to SSL stapling problems on the host. You can see some more details on that here:

How to address OCSP responder errors

Many of you have likely landed here due to running across the following error or similar in your Apache error log when sites using AutoSSL or other SSL certificates take an excessively long time to...

support.cpanel.net

as that is known to cause slowness only with https pages.

I'm not sure about the Git issue, but you're always welcome to put in a ticket with our team so we can take a look.

 

[OhFarts]

Hello

The slowness issue was "solved" by the hosting company (they just moved my website to another server ...).
But unfortunately, I still can't use "Deploy HEAD commit" which is greyed out.

The .cpanel.yml is still the same and I've just pulled updates to my Git repo a few minutes ago

Do you guys have any idea ?

 

[cPRex]

I'm glad the slowness issue turned out to be with the hosting and not with the cPanel tools.

It may be best to submit a ticket to our team so we can do some more investigation directly on your server for this particular issue.

 

[OhFarts]

I'm glad the slowness issue turned out to be with the hosting and not with the cPanel tools.

It may be best to submit a ticket to our team so we can do some more investigation directly on your server for this particular issue.

Hello cPRex

I'm using a shared hosting, I don't have any root access to the server. Am I able anyway to submit a ticket ?
My hosting company just told me they can't help and I have to contact you through this forum ...

 

[OhFarts]

More exciting news about this exciting (no) case :
Can't submit a request because I need the support ID which require root access to the server

 

[cPRex]

Correct - you'd need root access in order to submit a ticket with cPanel.

Your best bet would be to contact your hosting provider or datacenter. They can, in turn, contact us if that becomes necessary.