Error running app with default port #123

New Issue

2026-02-16T12:51:30-05:00

yindo commented

2026-02-16 12:51:30 -05:00

Originally created by @EatonEmmerich on GitHub (Nov 1, 2025).

I am running a custom domain.
I have updated my compose file to remove Caddy as I couldn't get it working and duplicated the configuration on Traefik instead.

After some configuration changes I got the app running and routed correctly, but I am getting the following error opening the login page:


XHROPTIONS
https://reporting.revolt.chat/
CORS Missing Allow Origin

	
OPTIONS
	https://reporting.revolt.chat/
Status
500
VersionHTTP/2
Transferred545 B (0 B size)
Referrer Policystrict-origin-when-cross-origin
DNS ResolutionSystem

    	
    alt-svc
    	h3=":443"; ma=86400
    cf-cache-status
    	DYNAMIC
    cf-ray
    	997b3cd27d8373e0-JNB
    content-length
    	105
    content-type
    	text/plain; charset=utf-8
    date
    	Sat, 01 Nov 2025 12:01:27 GMT
    nel
    	{"report_to":"cf-nel","success_fraction":0.0,"max_age":604800}
    report-to
    	{"group":"cf-nel","max_age":604800,"endpoints":[{"url":"https://a.nel.cloudflare.com/report/v4?s=ziGf0ZUdQqFnMsy6S1CthuteIWyBKp9MAFjbTIJ6M9aFP4ghLtl21HOA%2FZeU1cI5yTjdk1274RC4JeiKNXisxwl5AUb7rqUqGGT9RW72rRLTymlAeg%3D%3D"}]}
    server
    	cloudflare
    X-Firefox-Spdy
    	h2
    	
    Accept
    	*/*
    Accept-Encoding
    	gzip, deflate, br, zstd
    Accept-Language
    	en-US,en;q=0.5
    Access-Control-Request-Headers
    	content-type
    Access-Control-Request-Method
    	POST
    Connection
    	keep-alive
    Host
    	reporting.revolt.chat
    Origin
    	https://stoat.metabee.co.za
    Priority
    	u=4
    Referer
    	https://stoat.metabee.co.za/
    Sec-Fetch-Dest
    	empty
    Sec-Fetch-Mode
    	cors
    Sec-Fetch-Site
    	cross-site
    User-Agent
    	Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:144.0) Gecko/20100101 Firefox/144.0

Screenshot of application error:

Originally created by @EatonEmmerich on GitHub (Nov 1, 2025). I am running a custom domain. I have updated my compose file to remove Caddy as I couldn't get it working and duplicated the configuration on Traefik instead. After some configuration changes I got the app running and routed correctly, but I am getting the following error opening the login page: ``` XHROPTIONS https://reporting.revolt.chat/ CORS Missing Allow Origin OPTIONS https://reporting.revolt.chat/ Status 500 VersionHTTP/2 Transferred545 B (0 B size) Referrer Policystrict-origin-when-cross-origin DNS ResolutionSystem alt-svc h3=":443"; ma=86400 cf-cache-status DYNAMIC cf-ray 997b3cd27d8373e0-JNB content-length 105 content-type text/plain; charset=utf-8 date Sat, 01 Nov 2025 12:01:27 GMT nel {"report_to":"cf-nel","success_fraction":0.0,"max_age":604800} report-to {"group":"cf-nel","max_age":604800,"endpoints":[{"url":"https://a.nel.cloudflare.com/report/v4?s=ziGf0ZUdQqFnMsy6S1CthuteIWyBKp9MAFjbTIJ6M9aFP4ghLtl21HOA%2FZeU1cI5yTjdk1274RC4JeiKNXisxwl5AUb7rqUqGGT9RW72rRLTymlAeg%3D%3D"}]} server cloudflare X-Firefox-Spdy h2 Accept */* Accept-Encoding gzip, deflate, br, zstd Accept-Language en-US,en;q=0.5 Access-Control-Request-Headers content-type Access-Control-Request-Method POST Connection keep-alive Host reporting.revolt.chat Origin https://stoat.metabee.co.za Priority u=4 Referer https://stoat.metabee.co.za/ Sec-Fetch-Dest empty Sec-Fetch-Mode cors Sec-Fetch-Site cross-site User-Agent Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:144.0) Gecko/20100101 Firefox/144.0 ``` Screenshot of application error: <img width="1620" height="2093" alt="Image" src="https://github.com/user-attachments/assets/100a66ca-acb7-4a4f-9728-24a267ebc62e" />

yindo commented

2026-02-16 12:51:31 -05:00

@EatonEmmerich commented on GitHub (Nov 1, 2025):

UPDATE: the cors policy is a red herring as it simply relates to reporting the actual error.
Running the revolt/client server on a different port using docker compose exec -it web sh and manually executing yarn run start:inject seems to give me a working login page.
UPDATE UPDATE: the working page only works if the server is no longer connected so it was a red herring in a red herring.
Currently still investigating.

@EatonEmmerich commented on GitHub (Nov 1, 2025): UPDATE: the cors policy is a red herring as it simply relates to reporting the actual error. Running the `revolt/client server` on a different port using `docker compose exec -it web sh` and manually executing `yarn run start:inject` seems to give me a working login page. UPDATE UPDATE: the working page only works if the server is no longer connected so it was a red herring in a red herring. Currently still investigating.

yindo commented

2026-02-16 12:51:31 -05:00

@EatonEmmerich commented on GitHub (Nov 1, 2025):

Update:
Got some more error output for what was attempting to be reported (but blocked by revolt) to reporting.revolt.chat:

@EatonEmmerich commented on GitHub (Nov 1, 2025): Update: Got some more error output for what was attempting to be reported (but blocked by revolt) to `reporting.revolt.chat`: TypeError: Cannot read properties of undefined (reading 'invite_only') at https://stoat.metabee.co.za/assets/Login.1f8632ae.js:1:12503 at https://stoat.metabee.co.za/assets/main.60a044fc.js:134:51775 at https://stoat.metabee.co.za/assets/main.60a044fc.js:134:50798 at trackDerivedFunction$1 (https://stoat.metabee.co.za/assets/main.60a044fc.js:114:20016) at er.track (https://stoat.metabee.co.za/assets/main.60a044fc.js:114:26622) at useObserver (https://stoat.metabee.co.za/assets/main.60a044fc.js:134:50774) at _$6.ar [as constructor] (https://stoat.metabee.co.za/assets/main.60a044fc.js:134:51745) at _$6.O$4 [as render] (https://stoat.metabee.co.za/assets/main.60a044fc.js:1:10247) at j$6 (https://stoat.metabee.co.za/assets/main.60a044fc.js:1:7692) at https://stoat.metabee.co.za/assets/main.60a044fc.js:1:2714

yindo commented

2026-02-16 12:51:31 -05:00

@Rattle22 commented on GitHub (Feb 13, 2026):

I think I have the same issue.
I use Caddy behind an nginx. Took me a while to get it working, but I am now getting through and have the exact same stack trace.
On a different issue, someone said to add /api in the .web.env, but I had that from the getgo.

@Rattle22 commented on GitHub (Feb 13, 2026): I think I have the same issue. I use Caddy behind an nginx. Took me a while to get it working, but I am now getting through and have the exact same stack trace. On a different issue, someone said to add /api in the .web.env, but I had that from the getgo.

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: stoatchat/self-hosted#123