Replies: 2 comments
-
|
seem related to #562 one should certainly be able to access it if the docker host is on a local network without having to deal with all the TLS shinenigans... if i have my reverse proxy which deals already with all the TLS stuff as single point, why should I be forced to setup all the TLS for syson as well, even i am not going to use it? Is there a simple workaround? |
Beta Was this translation helpful? Give feedback.
0 replies
-
|
Hello, Did you try with the spring option "server.forward-headers-strategy=NATIVE"? Based on what i've read from the spring documentation, it could help you. Regards, |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
installed
image: "${IMAGE_TAG:-eclipsesyson/syson:v2025.6.0}"
with docker compose
tried with firefox and edge and both get:
index-CC_9dKTx.js:353
Uncaught TypeError: crypto.randomUUID is not a function
at index-CC_9dKTx.js:353:8366
at index-CC_9dKTx.js:1:146
at index-CC_9dKTx.js:5278:4519
(anonymous) @ index-CC_9dKTx.js:353
(anonymous) @ index-CC_9dKTx.js:1
(anonymous) @ index-CC_9dKTx.js:5278
it loads the site, but it stays empty
Beta Was this translation helpful? Give feedback.
All reactions