all-in-one docker #3509
Closed
drguiritan
announced in
Announcements
Replies: 1 comment
-
Hi @drguiritan, I see you are just using HTTP for your nginx reverse proxy. This could cause issues with some browsers flagging the site as unsecure. Here are the relevant snippets for your reference docker-compose.yml
nginx/specify.training.saiab.ac.za.conf
|
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.
-
all-in-one_asset-server_1 /bin/sh -c ve/bin/python s ... Up 8080/tcp
all-in-one_mariadb_1 docker-entrypoint.sh --max ... Up 3306/tcp
all-in-one_nginx_1 /docker-entrypoint.sh ngin ... Up 0.0.0.0:80->80/tcp,:::80->80/tcp
all-in-one_redis_1 docker-entrypoint.sh redis ... Up 6379/tcp
all-in-one_report-runner_1 /docker-entrypoint.sh java ... Up 8080/tcp
all-in-one_specify6_1 /bin/sh -c rsync -a --dele ... Exit 0
all-in-one_specify7-worker_1 /opt/specify7/docker-entry ... Up 8000/tcp
all-in-one_specify7_1 /opt/specify7/docker-entry ... Up 8000/tcp
I've done up and running the docker images but when I access my host-machine ip address remotely the NGINX says error 502 BAD GATEWAY. Do I miss something? I'm not sure whether to touch the file nginx/specify.conf or something need to modify from nginx container. Your help is much appreciated.
Beta Was this translation helpful? Give feedback.
All reactions