I've looked into the docker-compose and found a new image
Not sure what it does and if I should include it into upgraded installation.
If I do - there is a parameter
I guess I should set it to
fileserver in case of one docker-compose?
the bug is during creation of S3 bucket credential creation. you can manually fix the URL in
WEB APP CLOUD ACCESS find the right
Host (Endpoint) field and add the missing colon.
we will release a fix to 1.9 soon.
Made an upgrade to the latest version from 1.5 and have stumbled upon an issue with webserver:
I am saving all artefacts to a custom s3 server. Used to work fine - saving and downloading them from webserver. Now I can now download anything that resides on s3 - getting the following errors in browser console:
Unable to parse "https None " as a whatwg URL.
ERROR EndpointError: Custom endpoint
https [None](//storage.yandexcloud.net) was not a valid URI
Back at 1.5 there was an issue with custom s3 endpoints - to treat those as custom one needed to specify a port at the end - even it it is 443 - maybe that's the case?
Hi GentleSwallow91 , I would highly recommend upgrading to 1.9 as it brings new also a new major feature (as well as minor bug fixes). I'm not sure about DB migration - there might be one or two. I suggest taking a look at the versions in between 🙂