Docker not working on Server?

[MarioFromTheFH]

I noticed a strange thing.
It is possible to run the SysON-Docker on my local computer but it won't work accessing the web-interface after I ran the docker-compose on a Server.

There's only a blank page in the web-browser. No Error-Message in the docker-logs.

However, in the Javascript-Console there is an error:
Uncaught TypeError: crypto.randomUUID is not a function

Not really sure how to interpret this.

I'm using the unmodified docker-compose.yaml:

version: "3.8"
services:
  database:
    image: postgres:12
    environment:
      POSTGRES_DB: postgres
      POSTGRES_USER: username
      POSTGRES_PASSWORD: password
    networks:
      - syson
  app:
    image: "${IMAGE_TAG:-eclipsesyson/syson:v2024.7.0}"
    ports:
      - "8080:8080"
    environment:
      SPRING_DATASOURCE_URL: jdbc:postgresql://database/postgres
      SPRING_DATASOURCE_USERNAME: username
      SPRING_DATASOURCE_PASSWORD: password
      SIRIUS_COMPONENTS_CORS_ALLOWEDORIGINPATTERNS: "*"
      SERVER_PORT: 8080
    depends_on:
      - database
    networks:
      - syson
networks:
  syson:

Any idea how to debug this?

[AxelRICHARD]

Hello,

Thank your for using SysON.

Yes, your problem is known and filed in the troubleshooting section of the official SysON documentation : https://doc.mbse-syson.org/syson/v2025.10.0/installation-guide/troubleshooting.html#_empty_page_in_web_browser

If you want to install SysON on a server and use it from other machines, you need to configure https first.

Regards,

[AxelRICHARD]

By the way, the most recent version of SysON is 2025.10.0.

[MarioFromTheFH]

Thank you, I tried this.

Now the error is:

Bad Request
This combination of host and port requires TLS.

Still no proper error in the logs.

JS logs now says:

Error: Promised response from onMessage listener went out of scope

[AxelRICHARD]

It's strange it should work.
Remember that after configuring the https, you should now access to your SysON server from your web browser with https://MY_SYSON_SERVER instead of http://MY_SYSON_SERVER.

If you done that and still have the problem, could you do the procedure again please?

Regards,