Fider Docker - Everything is a 404 error, 307, 200 - but no Fider #1095
Replies: 1 comment 4 replies
-
|
Rolled back to PR_1064. There was no "HOST_DOMAIN" in the provided Docker-Compose Template. Was this deprecated for "BASE_URL"?? Have yet to test whether it was the variable or the rollback to earlier version that really fixed things. |
Beta Was this translation helpful? Give feedback.
-
|
Tested:
Has anyone had similar??? |
Beta Was this translation helpful? Give feedback.
-
|
I'm late on this post but am running into similar issues. Were you ever able to resolve this? |
Beta Was this translation helpful? Give feedback.
-
|
Having the same issue. Anybody have a fix? |
Beta Was this translation helpful? Give feedback.
-
|
@dudztroyer I eventually was able to resolve my issue. Here is an issue that you can reference. Hope this helps. |
Beta Was this translation helpful? Give feedback.
-
Hey Team,
Not entirely sure where to drop this, bug or discussion (sorry in advance).
I've been trying to bring up an instance of Fider to explore: a non-profit application.
Docker Compose
->image: getfider/fider:stable
->image: postgres:12
Basically the Fider DC template, with some usual adjustments (I'm not completely green with respect to container runs). Can paste, but don't think it's relevant.
Repeated in 2 cases.
-> Docker Desktop
-> Production server, with Traefik on the front end. Stacks of other services running fine.
Both DB and Fider seem to come up fine, and I get my "http server started on :3000"
On PC I got multiple workers, here I see only one.
In both cases, I couldn't get to the startup page. PC showed blank root/signup.. and I just get a timeout in production.
On PC everything ends up a 404
In production GET requests result in 404's, then redirects (307), then 'success' messages (200) with not page served.
Looked over forum and docs.
I haven't struck this before:
Is there a part of config I missed?
PRODUCTION ENV
DOCKER DESKTOP
Beta Was this translation helpful? Give feedback.
All reactions