Docker Compose deployment with no proxy unable to login and setup page not showing

Support
1

I have…

  • Read the following guideline: Install on Docker | Squidex
  • Used code blocks with ``` to format my code examples like JSON or logs properly.

I’m submitting a…

  • Regression (a behavior that stopped working in a new release)
  • Bug report
  • Performance issue
  • Documentation issue or request

Current behavior

Expected behavior

Minimal reproduction of the problem

Current behavior

I have deployed Squidex using Docker with the docker-compose-noproxy file, and everything runs perfectly. I can access the page at http://<IP>:8080/ without any issues. However, when I click the “Login to Squidex” button, nothing happens—there’s a brief popup blink, but no login window appears.

On the other hand, when I access Squidex over HTTPS using my domain (with Apache2 set up as a reverse proxy), the login popup does appear, but it shows the following error:

error:invalid_request
error_description:The specified ‘redirect_uri’ is not valid for this client application.
error_uri:https://documentation.openiddict.com/errors/ID2043

``` version: ‘3.5’
services:
squidex_mongo:
image: “mongo:4.4”
volumes:
- /etc/squidex/mongo/db:/data/db
networks:
- internal
restart: unless-stopped

squidex_squidex:
image: “squidex/squidex:7”
ports:
- “8080:80”
environment:
- URLS__BASEURL=https://${SQUIDEX_DOMAIN}
- EVENTSTORE__TYPE=MongoDB
-EVENTSTORE__MONGODB__CONFIGURATION=mongodb://squidex_mongo
- STORE__MONGODB__CONFIGURATION=mongodb://squidex_mongo
- IDENTITY__ADMINEMAIL=${SQUIDEX_ADMINEMAIL}
- IDENTITY__ADMINPASSWORD=${SQUIDEX_ADMINPASSWORD}
- IDENTITY__GOOGLECLIENT=${SQUIDEX_GOOGLECLIENT}
- IDENTITY__GOOGLESECRET=${SQUIDEX_GOOGLESECRET}
- IDENTITY__GITHUBCLIENT=${SQUIDEX_GITHUBCLIENT}
- IDENTITY__GITHUBSECRET=${SQUIDEX_GITHUBSECRET}
- IDENTITY__MICROSOFTCLIENT=${SQUIDEX_MICROSOFTCLIENT}
- IDENTITY__MICROSOFTSECRET=${SQUIDEX_MICROSOFTSECRET}
healthcheck:
test: [“CMD”, “curl”, “-f”, “http://localhost:80/healthz”]
start_period: 60s
depends_on:
- squidex_mongo
volumes:
- /etc/squidex/assets:/app/Assets
networks:
- internal
restart: unless-stopped

networks:
internal:
driver: bridge
```

Environment

App Name:

  • Self hosted with docker
  • Self hosted with IIS
  • Self hosted with other version
  • Cloud version

Version: [VERSION]

Browser:

  • Chrome (desktop)
  • Chrome (Android)
  • Chrome (iOS)
  • Firefox
  • Safari (desktop)
  • Safari (iOS)
  • IE
  • Edge

Others:

2

Have you checked the chrome logs?

You have to run Squidex with https. Are you sure that your base url is correct?

3

Just went through this a couple of days ago, you need to get a certificate for the squidex domain (even a self signed cert will get you in with some warnings).
You can terminate the SSL connection at Apache or I used nginx and then connect from there over http on port 8080 to the squidex container. Your base url does have to be https://