Jannis Mattheis

Could you try out [v0.4.4](https://github.com/traggo/server/releases/tag/v0.4.4)

Yeah, you're right. The version 0.2.1 looks okay. So, docker probably changed something on the API that is used by traggo.

Fixed with 0.4.1.

Sounds like a valid use-case, let's wait for feedback from others, if this feature is useful to them.

Hey could you try configuring it like this? ``` version: "3" services: server: image: gotify/server:2.4.0 ports: - 8080:80 environment: - GOTIFY_SERVER_CORS_ALLOWORIGINS=[.*] volumes: - "./gotify_data:/app/data" ``` This works for me when...

Don't mix environment config and file config. I've updated the environment config in the docs https://gotify.net/docs/config could you retry it in this format? I've this docker-compose: ``` version: "3" services:...

Have a look at the browser console, it says why the CORS request fails. Headers like `Content-Type` and `X-Gotify-Key` must be whitelisted in cors. You can do this with `GOTIFY_SERVER_CORS_ALLOWHEADERS=[X-Gotify-Key,...

I'd say adding the allowheaders and allowmethods as defaults shoulds reasonable.

The UI still uses an older react-scripts version which uses the legacy openssl provider. if you're Nodejs > 16, then you've to add this env variable, and then execute `yarn...

Maybe, but it's probably better to remove the need for the legacy openssl version by updating the react-scripts dependency.