Skip to content
Start building
Back

Again Gitlab and "Signing key cannot be empty"

  • 0
  • Self Hosted
  • Functions
View on Discord
mimimi
27 Jan, 2024, 17:01

hello! I don't understand what I'm doing wrong. I have searched all forum threads on this problem. I have watched all the videos on youtube. I have read all the threads on discord. I've banged my head against the wall. It's not working.

Appwite - 1.4.13

Trace:

TypeScript

I am using Docker Swarm and Portainer to deploy appwrite.

I've inserted the private key into .env both as a single string \n and as a multi-line variant in "".

Nothing helps.

TL;DR
Developers are experiencing an issue with a Gitlab error saying "Signing key cannot be empty." They are using Docker Swarm and Portainer to deploy Appwrite. They have tried various solutions including adding the private key into the .env file both as a single string and as a multi-line variant, but nothing has worked so far. No solution has been provided.
Drake
27 Jan, 2024, 17:20

Portainer? And .env?

mimimi
27 Jan, 2024, 17:23

yes. command for deploy: export $(grep -v '^#' .env | xargs) && docker stack config -c docker-compose-swarm.yml && docker stack deploy -c docker-compose-swarm.yml appwrite

and in Portainer change private key on service Appwrite and Build

Drake
27 Jan, 2024, 17:45

Sorry can you clarify the portainer part? I'm not well versed with portainer

Reply

Reply to this thread by joining our Discord

Reply on Discord

Recommended threads

Need support?

Join our Discord

Get community support by joining our Discord server.

Join Discord

Get premium support

Join Appwrite Pro and get email support from our team.

Learn more