fvalle1
commented
1 month ago +1 I observe the same
Closed gabrielefronze closed 1 week ago
fvalle1
commented
1 month ago +1 I observe the same
gabrielefronze
commented
1 month ago UPDATE:
This seems to have fixed the thing on my on-prem setup:
yarn as for troubleshooting guide.npx nx database:reset as for troubleshooting guide.FRONT_BASE_URL seems to be necessary to make everything work. I set it to be the same as the other var SERVER_URL without the port and suddenly the webpage became accessible.
arpan-ny
commented
1 month ago +1 had the same bug
darekdesu
commented
1 month ago How did you create docker-compose file? The one used with self-hosted installation script (docs link) has fallback FRONT_BASE_URL to SERVER_URL if it's not set in .env file:
# https://github.com/twentyhq/twenty/blob/main/packages/twenty-docker/docker-compose.yml
environment:
...
SERVER_URL: ${SERVER_URL}
FRONT_BASE_URL: ${FRONT_BASE_URL:-$SERVER_URL}
timboozle
commented
1 month ago UPDATE:
This seems to have fixed the thing on my on-prem setup:
- I ran
yarnas for troubleshooting guide.- I ran
npx nx database:resetas for troubleshooting guide.- The
FRONT_BASE_URLseems to be necessary to make everything work. I set it to be the same as the other varSERVER_URLwithout the port and suddenly the webpage became accessible.- Stopped and restarted the compose without deleting the volumes.
- Seems to work.
Same issue and followed your steps exactly but no luck, unfortunately. I can enter my email but after that it's just a white screen. It may be worth mentioning that there are no errors in the console whatsoever.
EDIT: I have SIGN_IN_PREFILLED=true and when I log in as tim@apple.dev the whole app just works. Setting SIGN_IN_PREFILLED=false and going through the troubleshooting steps again, however, does not work. So no tim@apple.dev but also my own email is generating a white screen.
gabrielefronze
commented
1 month ago Hello,
Thanks for the feedback so far.
Let’s assume the self hosted version has something wrong caused by me. We’ll dive later on into that.
I get the same issue when I try to start the 7 day demo from the website directly as well.
FelixMalfait
commented
4 weeks ago Hey sorry for the delay, I missed this. I tried on other browsers but can't reproduce. Seems like a very serious issue indeed. Would you wind showing screenshots of your network tab? Seems like maybe main JS script is getting blocked?
gabrielefronze
commented
4 weeks ago Hey @FelixMalfait ,
With pleasure. What do you mean by "network tab"? I am currently using JS for development and have no issue so far. If you prefer we can set up a live call for me to show you what happens?
P.s. nice Feynman picture ;)
gabrielefronze
commented
4 weeks ago UPDATE: I just tried again to log in on your platform and now I got prompted with the plan selection form. It seems to be back to normal operation. I'll later test it on local deployment as well.
FelixMalfait
commented
4 weeks ago @gabrielefronze mmh too bad you can't reproduce it now. Would have loved to see it live :)
By network tab I meant this in your browsers' developer console:
Feel free to book anytime next week if it's still stuck by then!
gabrielefronze
commented
4 weeks ago Got it! I'm used to use that but calling it differently due to Safari bias 😄
I'll keep you posted!
EndlessUndo
commented
4 weeks ago @FelixMalfait I got the same issue and can reproduce it. Here is a screenshot of the network tab.
Hope this helps. Please let me know if you need something else!
luccamrofc
commented
3 weeks ago +1
aljazceru
commented
2 weeks ago same here, exactly the same problem as @EndlessUndo, clearly you're not respecting SERVER_URL everywhere @FelixMalfait and it then breaks the CORS leading to black site
self hosted deployment seems to be broken atm
Freebios
commented
2 weeks ago Hello there,
I just ran a fresh install an could not reproduce the issue out of the box.
I was able to get CORS issue by changing the SERVER_URL for something else than localhost:3000 and then accessing the website trough localhost:3000
FRONT_BASE_URL is to be used if you host your frontend and your backend independently (eg. on a bucket), bu default the backend serve the front and this variable is not needed.
Would you mind checking if removing FRONT_BASE_URL and setting SERVER_URL to the address you want to expose your app works?
Also, was there something unclear in the documentation that we could improve on that matter?
Thanks :)
FelixMalfait
commented
1 week ago Sorry I'll be closing this for now as we don't really have any good steps to reproduce locally. If anyone has clear steps to reproduce from a fresh install please let us know and I'll re-open. Thanks!
dancpluz
commented
1 week ago Had the same issue, I was trying to run a nginx reverse proxy to my local server and expose it for other people to use it. I'm using the default docker compose file. I was able to access it locally, (SERVER_URL=http://my-local-ip-:port) but externally people ran into the blank page, that's because it was trying to fetch data from a local ip on an external setting:
So I setup my SERVER_URL=http://mydomain-or-public-ip:port and worked fine externally, but the problem is I can't access it locally now because my router has NAT reflection, that means I can't access my own public ip and redirect to the local one. Also tried changing other environment variables but none worked out, FRONT_BASE_URL was unuseful aswell. So my suggestion is somehow make this server url dynamic depending on external or local environments, or create another variable for local access.
FelixMalfait
commented
6 days ago @dancpluz yes setting SERVER_URL=http://mydomain-or-public-ip:port is the right thing to do (FRONT_BASE_URL shouldn't be used except you want to host the frontend separately which we do on our cloud version but don't recommend for simple self-hosted installs). Not sure about your use-case to access it internally / not familiar with NAT reflection though. I feel like that would be a problem common to any application you expose and not specific to Twenty.
dmbr0
commented
5 days ago I am also running into this issue. I have my instance running behind a Caddy reverse proxy. I have tried setting SERVER_URL=http://crm.mydomain.com:3000 by itself. FRONT_BASE_URL and SERVER_URL and both with http:// and https://.
The error I get everytime is:
Access to fetch at 'http://localhost:3000/graphql' from origin 'https://crm.mydomain.com' has been blocked by CORS policy: Response to preflight request doesn't pass access control check: Redirect is not allowed for a preflight request.
dmbr0
commented
5 days ago I have also tried hard coding FRONT_BASE_URL and SERVER_URL. Seems the localhost isnt being changed somewhere? or being called somewhere?
Definitely wouldn't call this closed even if it's not reproducible at this point. People are still having an issue with it and think it would help if people could see this was still an issue to contribute to finding a way to reproduce it.
dmbr0
commented
5 days ago I was able to get rid of the CORS issue. it seems that referenced volumes were not being updated when changing the URL values. after deleting the volumes and recreating the application, the warning is gone but I am still getting a white screen just with no errors.
dmbr0
commented
4 days ago stopping the containers, removing old volumes and setting SERVER_URL to https://crm.mydomain.com without :3000 seems to have worked.
my question is why it happened in the first place as my SERVER_URL was set to this originally but the localhost was still coming up. it's like docker didn't take the .env variable.
aljazceru
commented
4 days ago doing everything from scratch as @dmbr0 suggested solved my issue too
Bug Description
Both a self-hosted copy I just ran via docker-compose and the official page (https://app.twenty.com/welcome) show the same behaviour.
This behaviour is present in multiple browsers and appears to be independent from that (Safari, Chrome, Firefox tested). Javascript is enabled on all such browsers.
EDIT: tested on my iPad as well and the behaviour is the same.
Expected behavior
I should be welcomed or taken to the create workspace wizard, but I have no clue since I never experienced the procedure due to the page being completely white.
Technical inputs
The HTML code of the welcome page is the following:
The script from Cloudflare is actually there.