[cpbackup_transporter] Path creation failed: AuthorizationHeaderMalformed: The authorization header is malformed; the region
Been seeing this error popup for random accounts over the last few weeks in the cptransport log and it has never been an issue in the last few years. Anyone else?
warn [cpbackup_transporter] Path creation failed: AuthorizationHeaderMalformed: The authorization header is malformed; the region 'us-east-1' is wrong; expecting 'us-east-2'
-
Hey hey! I haven't heard of this being a widespread issue, so is it possible something changed on the destination side's configuration?
0 -
not that I am aware of sir, I'll let you know early next week if it happens again. I have lowered the concurrent connections and added cloudflare and google as the default resolvers.
0 -
I did fine one other event where this happened and our team created a case!
so you can follow along with that page for updates.
0 -
We have the same issues since a couple of weeks;
[2025-11-11 02:22:32 -0500] warn [cpbackup_transporter] Path creation failed: AuthorizationHeaderMalformed: The authorization header is malformed; the region 'us-east-1' is wrong; expecting 'ca-central-1' [2025-11-11 02:24:39 -0500] warn [cpbackup_transporter] Path creation failed: AuthorizationHeaderMalformed: The authorization header is malformed; the region 'us-east-1' is wrong; expecting 'ca-central-1' [2025-11-11 02:26:45 -0500] warn [cpbackup_transporter] Path creation failed: AuthorizationHeaderMalformed: The authorization header is malformed; the region 'us-east-1' is wrong; expecting 'ca-central-1'It seems pretty much random, it affects a few accounts during backup routines.
0 -
Thank you schoeps for reporting this - your post came up on a search, so I know we're not alone.
We're seeing this, in recent weeks like others, across a variety of servers all running cP 130 with OS and other components kept completely up to date. I should say that we are using "proper" S3 rather than a compatible clone - and it's an official, normal S3 region that we use.
Each night a different few user accounts fail to back up. Some in that night's batch will be uploaded fine but others don't, because of the error kj quoted (different expected region though).
If something is set up wrong at the S3 end, surely it would fail for all user accounts?
0 -
cPRex, since the backups are created but not sent, is there a reccomended script to run the transporter and prune the files?
0 -
That's a great question, but I don't have such a tool available.
0 -
is it possible to trigger /usr/local/cpanel/bin/cpbackup_transporter with some arguements?
0 -
It won't operate by itself, no. It only runs when the full backup system is called.
0 -
Looks like it’s getting worse, more backups missed. Should i create a ticket?
0 -
Also had this issue since the 17th October.
Was usually a couple of accounts each day, but the past 3 days it has been many more accounts failing. Still random and not the same accounts each day.0 -
Also been having this issue since November 5th. Never had issues like this before and didn't change any settings in cPanel or the S3 bucket.
0 -
Update - I did reach out to the development team and it is on their radar now. While this is an older case it seems that a change on the Amazon side is making this a more critical issue.
I've also tagged this thread to case CPANEL-40311 so I'll post any updates I get!
2 -
thanks! :) <3 <3 <3
0 -
Of course!
0 -
Yes, I'm having the same issue. It started off as 3-4 failures, now it's 20-30. It's also random, what failed the night prior is okay the next day and vice versa.
0 -
As mentioned in the other thread, I began seeing this issue around mid-October. It’s affecting two separate VPS servers running cPanel, hosted by different vendors on different U.S. networks. Prior to this, backups to AWS S3 ran without any issues. Looking forward to an update on this.
0 -
Just a head up for folks experiencing this issue, since part of the transporter script is to delete the local files post transfer, these backups are not deleted which could cause you to run into disk issues. Be sure to download/delete those untransferred files! Hoping we see some resolution to this soon! Please!
0 -
Not sure if a hotfix was applied recently, but all 10 servers backed up last night with no errors...
0 -
That's great schoeps - unfortunately our overnight S3 run was one of the worst ever! I imagine any fix will be part of a numbered version with an entry in the change log.
0 -
Can confirm we are seeing the same issue across multiple servers.
Backup to S3 has been running fine nightly for years, problems are recent and the same as outlined above.0 -
Running 130.0.16 over here.
0 -
schoeps - no changes on our end for this one, so maybe you just had a lucky run?
0 -
sounds like it...
0 -
Is there any movement on this? I am having the same problem and it's becoming critical now. The back-ups that get this error are random but my two servers always skip a few accounts every time it runs.
1 -
Ian - nothing substantial at this point, other than it is being worked on. The team knows the cause of the issue and is coming up with the best way to fix the broken behavior.
0 -
I decided to try an obvious fix in the meantime while we wait for cPanel to permanently fix the problem. I created a new bucket in the us-east-1 region and set the backups for that. It worked fine with all accounts backed up and transferred.
0 -
Update - our team has a fix in place that's currently going through testing, so hopefully this gets released soon!
2 -
@cPRex Thanks for the update.
0
Please sign in to leave a comment.
Comments
44 comments