Server Replied "504 Gateway Timeout" #706
-
How to use GitHub
Steps to reproduce
Expected behaviorUpload without Errors Actual behaviorUploads with errors "Server Replied "504 Gateway Timeout"" Host OSUbuntu 20.04 Nextcloud AIO versionv1.1.0 Current channelYou are running the latest channel. Other valuable infoLog in the WebUI is empty |
Beta Was this translation helpful? Give feedback.
Replies: 9 comments
-
How long did the transfer need and are you running aio behind a reverse proxy? |
Beta Was this translation helpful? Give feedback.
-
I need to oberve the exact behavior.. But waht I saw, ist that the Upload from the affected file is stopped and marked with a red cross. After the next Nextcloud Desktop boot, it will mark as "sync"(green hack). |
Beta Was this translation helpful? Give feedback.
-
How long did the upload take? |
Beta Was this translation helpful? Give feedback.
-
Beta Was this translation helpful? Give feedback.
-
Thanks! Can you send the apache container logs and the nextcloud container logs as well as the nextcloud logs from directly after the problem happens? Thank you! |
Beta Was this translation helpful? Give feedback.
-
Also, can you send your reverse proxy conf? The default haproxy timeout may be the issue here... |
Beta Was this translation helpful? Give feedback.
-
I just tried on my testinstance without reverse proxy and it successfully uploaded a 7GB file without any timeout in 25min. |
Beta Was this translation helpful? Give feedback.
-
Hello @david-steg any update here? |
Beta Was this translation helpful? Give feedback.
Hello @david-steg any update here?