Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Awaiting response ... 404 not found using Envoyer deployment

Don Jones
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
October 19, 2023

The folks over at told me the issue we are having is on Bitbucket's side. This is the error message we are receiving when trying to deploy from Envoyer.

Downloading the code repository.
Found tarball URL:
--2023-10-19 23:54:41--
Resolving (,,, ...
Connecting to (||:443... connected.
HTTP request sent, awaiting response... 404 Not Found
2023-10-19 23:54:41 ERROR 404: Not Found.

Any tips or ideas I can try?

1 answer

0 votes
Theodora Boudale
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
October 20, 2023

Hi Don and welcome to the community!

Are you using a wget command to get the tar.gz file with the repo's source code?

If so, the most likely reason for this error is that we return a 404 error code for unauthenticated requests. The wget command always waits for the 403 challenge from the server before it sends the credentials to the server. However, our server initially sends a 404 status to the client and wget doesn't send credentials later on.

You can use the --auth-no-challenge flag with the wget command to solve this issue.

Alternatively, you could also use curl to download the file.

Please feel free to let me know how it goes and if you have any questions.

Kind regards,

Suggest an answer

Log in or Sign up to answer
AUG Leaders

Atlassian Community Events