It’s a standard non-docker installation using the standalone Go binary
It happens against the AWS backend storage
No special characters involved.
Split feature is set to 5MB chunks (when a file is bigger than 100MB)
After further investigation we found that “small files” (under the 100 MB) upload successfully. But as soon as a file needs chunking we starting getting the AWS upload error.
Hi Raf,
can you tell (again?) more about your proxy. This is 99% of the time an issue with the request Host header being carried out through a proxy.
-c
No proxy (except Cloudflare). It’s all within cells Go binary (including SSL), no Apache nor Nginx nor docker involved.
(Is there a ./cells command to dump the internal httpd configuration if that’s of any use for you?)
sorry @drzraf Covid is hitting the team …
How do you access to the instance, with an IP or a domain ? In the latter case, did you properly configure the external URL with cells configure sites?
cells is using a domain-name (and everything is working fine except chunked-upload)
I never ran cells configure sites since I upgraded from a previous v2 version where this command was not necessary.
I think my installation was: cells install --bind mydomain.org:443 --external https://mydomain.org --le_email foo@mydomain.org --le_agree true
But running now ./cells configure sites gives
The following sites are currently defined:
+---+--------------------------+--------------+--------------------------+
| # | BIND(S) | TLS | EXTERNAL UR |
+---+--------------------------------------+--------------+--------------+
| 0 | https://mydomain.org:443 | Lets Encrypt | https://mydomain.org:443 |
+---+--------------------------+--------------+--------------------------+
Regarding DNS, resolveip mydomain.org resolves to Cloudflare addresses.
Sadly, since cells is handling it’s SSL decryption itself I can’t hook and provide you tcpdump/unencrypted traffic/HTTP headers as received by it (unless there is a built-in detailed logging mechanism inside cells)