502 Bad Gateway - Login Error (docker version)

themisterbondy · January 28, 2019, 9:25pm

Is it an existing mongodb database!

Sebastian · January 28, 2019, 9:27pm

Is there something in the nginx logs?

Sebastian · January 28, 2019, 9:32pm

It could be this problem: Identity Server changed? Can't login to Squidex UI problem

Have to update the docker-compose files

themisterbondy · January 28, 2019, 9:34pm

https://1drv.ms/t/s!AunVZ486YZmdidkGfDsjOjm9A58Z9w

Sebastian · January 28, 2019, 9:35pm

yepp, I see it in the logs.

themisterbondy · January 28, 2019, 9:39pm

Where do I create this?

Blockquote
Add this to your ingress manifest:
“nginx.ingress.kubernetes.io/proxy-buffer-size”: “8k”

Sebastian · January 28, 2019, 9:40pm

Do you use the default docker-compose files?

themisterbondy · January 28, 2019, 9:41pm

Yes I am use the default docker-compose files !!!

Sebastian · January 28, 2019, 9:41pm

I will provide a fix soon, just wait 10 min or so.

Sebastian · January 28, 2019, 9:44pm

I pushed something, can you try the new docker-compose?

themisterbondy · January 28, 2019, 9:45pm

Aeeeee !!! I’ll wait, no problem!

Thank you very much

themisterbondy · January 28, 2019, 9:47pm

Yes, no problem!!!

Where do I get it?

Sebastian · January 28, 2019, 9:47pm

Same repository, where did you get the other docker-compose file from?

themisterbondy · January 28, 2019, 9:49pm

From here…

github.com

Squidex/squidex-docker/blob/master/standalone/docker-compose.yml

version: '2.1'
services:
  squidex_mongo:
    image: mongo:latest
    ports:
      - "27017:27017"
    volumes:
      - /etc/squidex/mongo/db:/data/db
    networks:
      - internal
    restart: unless-stopped

  squidex_squidex:
    image: "squidex/squidex:latest"
    ports:
      - "5000:80"
    environment:
      - URLS__BASEURL=${SQUIDEX_PROTOCOL}://${SQUIDEX_DOMAIN}/
      - URLS__ENFORCEHTTPS=${SQUIDEX_FORCE_HTTPS}
      - EVENTSTORE__CONSUME=true

This file has been truncated. show original

Sebastian · January 28, 2019, 9:50pm

Yes, this contains the fix.

themisterbondy · January 28, 2019, 9:51pm

I’ll test thank you!!

Sebastian · January 28, 2019, 9:58pm

Does it work? It is already late here in Germany.

themisterbondy · January 28, 2019, 10:05pm

He ran and stopped the nginx, strange.
Is this right?

docker ps -a
CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES
74e050678296 jrcs/letsencrypt-nginx-proxy-companion “/bin/bash /app/entr…” 3 minutes ago Up 3 minutes standalone_squidex_encrypt_1
3c5f2e33b7f0 squidex/nginx-proxy “/app/docker-entrypo…” 3 minutes ago Exited (0) 3 minutes ago standalone_squidex_proxy_1
e6a7bcf575ff squidex/squidex:latest “./Squidex” 3 minutes ago Up 3 minutes 33333/tcp, 40000/tcp, 0.0.0.0:5000->80/tcp standalone_squidex_squidex_1
7ebb6f6cec6e mongo:latest “docker-entrypoint.s…” 3 minutes ago Up 3 minutes 0.0.0.0:27017->27017/tcp standalone_squidex_mongo_1
rogerio@MyDockerVM:~/squidex-docker-master/standalone$

Sebastian · January 28, 2019, 10:07pm

No, it is not by purpose. I havent had the time to yet to test it. Will do it tomorrow and let you know

themisterbondy · January 28, 2019, 10:10pm

Okay, no problem, for today, thank you very much, let’s rest, it’s already late here in Brazil too.
We talk tomorrow
Thank you !