“403 forbidden” issue suddenly happening

Hey @deeve007

It might be that you downloaded a different installer than was built with the archive file. Inside the archive.zip is an exact copy of the installer named installer-backup.php in case you lost the original. If you want to submit a support ticket for this issue we can have a closer look at your setup. Please provide a link to this thread when submitting the ticket.

Thanks~

In the other support thread (now closed) you asked this:

– The installer is showing blank/white, 403, 404 or a 500 error?
– https://snapcreek.com/duplicator/docs/faqs-tech/#faq-installer-013-q

It’s showing a 403 error, and I submitted a ticket to my host and all they said was it’s your plugin’s issue, they simply told me to change the file permission settings manually, which then lead to other problems it seems.

ie, this one: https://zavahost.com/temp/duplicator-bug.jpg

So I think there’s a link here, maybe something on the host end, but I don’t know what to suggest to them, and they don’t have much interest in investigating what they believe is a plugin issue.

I’ll submit a support ticket in your system and hopefully we can get to the bottom of this.

The explanation my host is trying to give:

—–
The problem is with the compression. As soon as we uncompress the compressed file provided the permissions are incorrect (files 666/folder 777). Nothing has changed at our end that would cause such an issue.

If you compress a folder/file on your account and then extract it the permissions will be the same. We tested that and the permissions don’t change to 666/777.
—–

This is despite it working fine on the exact same server for the past 2+ years, even until earlier this week, the issue only appearing for the first time today.

Hey @deeve007,

I see your ticket has been assigned to one of the developers and they will look at it as soon as they can.

Thanks~

So, after HOURS of my time wasted (from my web host denying it was their end), and then some great help from Duplicator support, it turns out the issue was on my web host’s end.

Advice from duplicator support to pass onto my host:
“I speculate that there was an umask value issue. Generally, the umask value is 022 so a folder is created with 0755 and a file with 0644. Kindly contact your hosting provider to know your server’s unmask value and then ask them to set the unmask value to the 022.”

My host’s reply, a few hours after I had sent them the above:
“This seems to be a bug in CageFS and we will contact CloudLinux for them to fix it in their next update.”

Appreciate the help given to me by Duplicator support.
Less so the many hours wasted while my web host refused to consider it could be their end, while I repeated numerous tests showing it must have been yet they still refused to look into it further until the information from Duplicator support.

Hey @deeve007,

Thanks for the update! We are glad you were able to get things going again…

Cheers~