Hi @Danel Senior, welcome to the community.
Are there any other systems between you and your bitbucket server, such as a reverse proxy that's doing the TLS work? I wonder if the timeout is a symptom and if the proxy is masking the actual problem.
There are a surprising number of adjustable timeout values in bitbucket.properties. If we can identify from the logs which timeout is being triggered, you can adjust the timeout value and it might solve your symptoms. About how long does the API call run before returning that 504?
If it's around 2 minutes, it might be this one:
Process execution
Controls timeouts for external processes, such as git.
| Default value |
Description |
process.timeout.execution
|
120 |
Configures a hard upper limit on how long the command is allowed to run even if it is producing output.
This value is in seconds. Using 0, or a negative value, disables the timeout completely.
|
process.timeout.idle
|
60 |
The idle timeout configures how long the command is allowed to run without producing any output.
This value is in seconds. Using 0, or a negative value, disables the timeout completely.
|
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.