Replies: 3 comments 7 replies
-
Hi, Claris changed the port for the admin console to the https port 443, so that is correct behaviour. What did you need to change to run fms 19.4.2? And could you post the results of your scan? Did you you do a scan prior to 19.4.2 with no or less reported vulnerabilities? Greetings, |
Beta Was this translation helpful? Give feedback.
-
Hello, I changed the part in the README, thanks for pointing out. As for the scan results, the vulnerabilities found are in Ubuntu system packages and node, amongst others, and I don't maintain these. I'm sure they were there in prior images, since they are independent from the fms version installed. You could scan the official ubuntu:18.04 image to double check. So long, |
Beta Was this translation helpful? Give feedback.
-
Hi, I tried to follow Claris' and your instructions and I keep on having unmet dependencies.[ Any ideas? Thanks. |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
Hi fmgarage,
I tried to change something related to the filemaker_server package in .env, install.sh, helper_ubuntu.sh and copy new .deb file for FMS 19.4.2.
It worked, but I did not know what were going wrong with the container such as port 16000 for admin-console did not run as usual instead of 16000, admin-console run on port 443,..it has about 20 medium vulnerabilities after I scan Docker.
Please arrange your time to release new update for FMS 19.4.2
Thank you very much
Beta Was this translation helpful? Give feedback.
All reactions