Troubleshooting

The most common malfunctions that may come up when using the Secretium.

🤔 Can't find the answer here?

Feel free to create an issue or start a discussion in the Secretium project repository. And, of course, we would be happy if you could send a PR with suggestions for improving the docs.

The requested image's platform does not match the detected host platform

The Secretium project aims to deploy the instance in the cloud (or any remote server), therefore the official Docker image is available for GNU/Linux only:

• linux/amd64
• linux/arm64

Other architectures and operating systems are not supported.

Windows Subsystem for Linux

Yes, Secretium perfectly works on the Windows Subsystem for Linux (WSL) too, because it uses Ubuntu as the GNU/Linux distro.

Port X is taken by OS

Some operating systems may take up ports that you want to use to develop and deploy your application. You can check if a port is taken by OS by running the command:

GNU/Linux

lsof -iTCP -sTCP:LISTEN -P

macOS

lsof -iTCP -sTCP:LISTEN -P

Windows

netstat -aon

To change the port number, edit the docker-compose.yml file:

1. Replace <CONTAINER_PORT> with the port number you want to use for the container.
2. Replace <SERVER_PORT> with the same port number as the exposed container port (<CONTAINER_PORT>).

services:
  secretium:
    # ...
    expose:
      - '<CONTAINER_PORT>'
    environment:
      # ...
      SERVER_PORT: <SERVER_PORT>

# ...

Next, just re-build the Secretium container to apply the changes:

docker-compose up -d --build --force-recreate

And now, define the new container port in your proxy/web server.