White screen on first load... #412

New issue

Open

opened 2026-05-13 14:13:53 -05:00 by MTFisher93 · 2 comments

MTFisher93 commented

2026-05-13 14:13:53 -05:00

(Migrated from github.com)

   environment:
     POSTGRES_USER: voidauth
     POSTGRES_PASSWORD: VoidAuthPass123
     POSTGRES_DB: voidauth

   volumes:
     - db:/var/lib/postgresql/data

   healthcheck:
     test: ["CMD-SHELL", "pg_isready -U voidauth"]
     interval: 10s
     timeout: 5s
     retries: 5

   voidauth:
     image: voidauth/voidauth:latest
     container_name: voidauth
     restart: unless-stopped

   depends_on:
     db:
       condition: service_healthy

   ports:
    - "3000:3000"

   environment:
     APP_URL: https://auth.MYDOMAIN.com

     STORAGE_KEY: KEY_HERE

     DB_HOST: db
     DB_PORT: 5432
     DB_NAME: voidauth
     DB_USER: voidauth
     DB_PASSWORD: VoidAuthPass123

     TZ: America/Indiana/Indianapolis

   volumes:
    db:

Here is the errors I get in the Console of the webpage:
The Cross-Origin-Opener-Policy header has been ignored, because the URL's origin was untrustworthy. It was defined either in the final response or a redirect. Please deliver the response using the HTTPS protocol. You can also use the 'localhost' origin instead. See https://www.w3.org/TR/powerful-features/#potentially-trustworthy-origin and https://html.spec.whatwg.org/#the-cross-origin-opener-policy-header. reset_password?id=ad1bb682-38d2-4c71-ae19-866da5d74d7f&challenge=eS2bz9hdJEdfB3VWqUCfJKdeG12F2sdN:1 The page requested an origin-keyed agent cluster using the Origin-Agent-Cluster header, but could not be origin-keyed since the origin 'http://192.168.1.117:3000' had previously been placed in a site-keyed agent cluster. Update your headers to uniformly request origin-keying for all pages on the origin. material-icons.css:1 Failed to load resource: net::ERR_SSL_PROTOCOL_ERROR flag-emojis.css:1 Failed to load resource: net::ERR_SSL_PROTOCOL_ERROR generated-mat-theme.css:1 Failed to load resource: net::ERR_SSL_PROTOCOL_ERROR custom.css:1 Failed to load resource: net::ERR_SSL_PROTOCOL_ERROR styles-QGFGL6UG.css:1 Failed to load resource: net::ERR_SSL_PROTOCOL_ERROR chunk-6SHD4QOO.js:1 Failed to load resource: net::ERR_SSL_PROTOCOL_ERROR chunk-VCQYX2XT.js:1 Failed to load resource: net::ERR_SSL_PROTOCOL_ERROR chunk-YJXGBADE.js:1 Failed to load resource: net::ERR_SSL_PROTOCOL_ERROR chunk-ARHNVZPX.js:1 Failed to load resource: net::ERR_SSL_PROTOCOL_ERROR chunk-264TIBIR.js:1 Failed to load resource: net::ERR_SSL_PROTOCOL_ERROR chunk-C46IYIWU.js:1 Failed to load resource: net::ERR_SSL_PROTOCOL_ERROR chunk-KZAQ56RO.js:1 Failed to load resource: net::ERR_SSL_PROTOCOL_ERROR chunk-OMYHIQWJ.js:1 Failed to load resource: net::ERR_SSL_PROTOCOL_ERROR polyfills-5CFQRCPP.js:1 Failed to load resource: net::ERR_SSL_PROTOCOL_ERROR main-GMVTGYQF.js:1 Failed to load resource: net::ERR_SSL_PROTOCOL_ERROR :3000/favicon.svg:1 Failed to load resource: net::ERR_SSL_PROTOCOL_ERROR :3000/apple-touch-icon.png:1 Failed to load resource: net::ERR_SSL_PROTOCOL_ERROR reset_password?id=ad1bb682-38d2-4c71-ae19-866da5d74d7f&challenge=eS2bz9hdJEdfB3VWqUCfJKdeG12F2sdN:1 Unsafe attempt to load URL https://192.168.1.117:3000/reset_password?id=ad1bb682-38d2-4c71-ae19-866da5d74d7f&challenge=eS2bz9hdJEdfB3VWqUCfJKdeG12F2sdN from frame with URL http://192.168.1.117:3000/reset_password?id=ad1bb682-38d2-4c71-ae19-866da5d74d7f&challenge=eS2bz9hdJEdfB3VWqUCfJKdeG12F2sdN. Domains, protocols and ports must match.

Any help would be appreciated.

I am configuring for the first time and when I go to the admin password reset link given in the logs it returns a white page and gives me nothing. This has happened for both a public app url I have set and configured in cloudflare and in nginx proxy manager, as well as when I set it to local IP and restarted. I cannot get to the any type of web interface to get started. Here is my compose: services: db: image: postgres:16 container_name: voidauth-db restart: unless-stopped environment: POSTGRES_USER: voidauth POSTGRES_PASSWORD: VoidAuthPass123 POSTGRES_DB: voidauth volumes: - db:/var/lib/postgresql/data healthcheck: test: ["CMD-SHELL", "pg_isready -U voidauth"] interval: 10s timeout: 5s retries: 5 voidauth: image: voidauth/voidauth:latest container_name: voidauth restart: unless-stopped depends_on: db: condition: service_healthy ports: - "3000:3000" environment: APP_URL: https://auth.MYDOMAIN.com STORAGE_KEY: KEY_HERE DB_HOST: db DB_PORT: 5432 DB_NAME: voidauth DB_USER: voidauth DB_PASSWORD: VoidAuthPass123 TZ: America/Indiana/Indianapolis volumes: db: Here is the errors I get in the Console of the webpage: `The Cross-Origin-Opener-Policy header has been ignored, because the URL's origin was untrustworthy. It was defined either in the final response or a redirect. Please deliver the response using the HTTPS protocol. You can also use the 'localhost' origin instead. See https://www.w3.org/TR/powerful-features/#potentially-trustworthy-origin and https://html.spec.whatwg.org/#the-cross-origin-opener-policy-header. reset_password?id=ad1bb682-38d2-4c71-ae19-866da5d74d7f&challenge=eS2bz9hdJEdfB3VWqUCfJKdeG12F2sdN:1 The page requested an origin-keyed agent cluster using the Origin-Agent-Cluster header, but could not be origin-keyed since the origin 'http://192.168.1.117:3000' had previously been placed in a site-keyed agent cluster. Update your headers to uniformly request origin-keying for all pages on the origin. material-icons.css:1 Failed to load resource: net::ERR_SSL_PROTOCOL_ERROR flag-emojis.css:1 Failed to load resource: net::ERR_SSL_PROTOCOL_ERROR generated-mat-theme.css:1 Failed to load resource: net::ERR_SSL_PROTOCOL_ERROR custom.css:1 Failed to load resource: net::ERR_SSL_PROTOCOL_ERROR styles-QGFGL6UG.css:1 Failed to load resource: net::ERR_SSL_PROTOCOL_ERROR chunk-6SHD4QOO.js:1 Failed to load resource: net::ERR_SSL_PROTOCOL_ERROR chunk-VCQYX2XT.js:1 Failed to load resource: net::ERR_SSL_PROTOCOL_ERROR chunk-YJXGBADE.js:1 Failed to load resource: net::ERR_SSL_PROTOCOL_ERROR chunk-ARHNVZPX.js:1 Failed to load resource: net::ERR_SSL_PROTOCOL_ERROR chunk-264TIBIR.js:1 Failed to load resource: net::ERR_SSL_PROTOCOL_ERROR chunk-C46IYIWU.js:1 Failed to load resource: net::ERR_SSL_PROTOCOL_ERROR chunk-KZAQ56RO.js:1 Failed to load resource: net::ERR_SSL_PROTOCOL_ERROR chunk-OMYHIQWJ.js:1 Failed to load resource: net::ERR_SSL_PROTOCOL_ERROR polyfills-5CFQRCPP.js:1 Failed to load resource: net::ERR_SSL_PROTOCOL_ERROR main-GMVTGYQF.js:1 Failed to load resource: net::ERR_SSL_PROTOCOL_ERROR :3000/favicon.svg:1 Failed to load resource: net::ERR_SSL_PROTOCOL_ERROR :3000/apple-touch-icon.png:1 Failed to load resource: net::ERR_SSL_PROTOCOL_ERROR reset_password?id=ad1bb682-38d2-4c71-ae19-866da5d74d7f&challenge=eS2bz9hdJEdfB3VWqUCfJKdeG12F2sdN:1 Unsafe attempt to load URL https://192.168.1.117:3000/reset_password?id=ad1bb682-38d2-4c71-ae19-866da5d74d7f&challenge=eS2bz9hdJEdfB3VWqUCfJKdeG12F2sdN from frame with URL http://192.168.1.117:3000/reset_password?id=ad1bb682-38d2-4c71-ae19-866da5d74d7f&challenge=eS2bz9hdJEdfB3VWqUCfJKdeG12F2sdN. Domains, protocols and ports must match.` Any help would be appreciated.

👀 1

notquitenothing commented

2026-05-15 17:08:03 -05:00

(Migrated from github.com)

It seems like you are getting SSL/HTTPS/Certificate errors, are you accessing your instance (what is shown in the URL bar of your browser) from the same URL as what is in your APP_URL variable?

It seems like you are getting SSL/HTTPS/Certificate errors, are you accessing your instance (what is shown in the URL bar of your browser) from the same URL as what is in your `APP_URL` variable?

👍 1

mv-fs commented

2026-05-18 11:56:57 -05:00

(Migrated from github.com)

To extend on the previous reply, I have met this same error in the past. To fix you not only do you need to access the VoidAuth instance from the same URL as you added in the environment variable APP_URL, but you need to make sure this domain has proper certificates with it.
For example, if you use Cloudflare, check that Cloudflare is set as the authority to provide certificates for that domain.
If you use Nginx and Let'sEncrypt, make sure they are properly configured for the domain you use as APP_URL.

And btw just in case, the APP_URL needs to use the "https" protocol, it will not work with HTTP (at least from my experience)

To extend on the previous reply, I have met this same error in the past. To fix you not only do you need to access the VoidAuth instance from the same URL as you added in the environment variable APP_URL, but you need to make sure this domain has proper certificates with it. For example, if you use Cloudflare, check that Cloudflare is set as the authority to provide certificates for that domain. If you use Nginx and Let'sEncrypt, make sure they are properly configured for the domain you use as APP_URL. And btw just in case, the APP_URL needs to use the "https" protocol, it will not work with HTTP (at least from my experience)