Closed CiTRuS93 closed 4 years ago
Hi,
The intire error trace says that there is a circular placehoder reference within the spring configuration key "sebserver.webservice.http.external.port". Can you please check if the right port number is set for this key within the config/application-xy.properties file in your specific SEB Server docker setup directory. Which particulare SEB Server docker setup do you use, demo, testing or productive?
Best, Andreas
thank I'll check it! I'm using demo setup but I need to run the server on different port then 8080. I changed the port on the yaml file and the properties file.
Yes this should work. I've also found an error from our side that causes the circular placehoder reference issue within the newest repository version and corrected it.
But anyway, if it is still not working please make sure you checkout the latest stable version of SEB Server with this command: git clone -b v1.0-latest https://github.com/SafeExamBrowser/seb-server-setup.git and start from there. Make also sure that you only change the port mapping in the yaml file and let the internal docker port stay 8080. For example if you want to map the server to port 8090:
seb-server:
build:
context: .
args:
- SEBSERVER_VERSION=1.0-latest
container_name: seb-server
environment:
- SERVER_PORT=8080
- SERVER_PWD=somePW
volumes:
- ./config:/sebserver/config
- seb-server-logs:/sebserver/log
ports:
- 8090:8080
- 9090:9090
networks:
- ralph
depends_on:
- "mariadb"
Please let me know if it doesn't work. I will then test it on my own windows machine and check your case in detail.
thanks! every thing work perfectly good now!
Describe the bug Docker keep failing during demo set up
To Reproduce Steps to reproduce the behavior:
docker-compose up -d
2.server keep restartingExpected behavior Server start's normally
Setup (please complete the following information): --window 10 Home -- SEB 1.0.0
keep getting this exception:
attaching the container log: