-
Notifications
You must be signed in to change notification settings - Fork 260
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
504 Timeout when trying to open expose.mydomain.com/users #18
Comments
Can you try modifying the When clicking the user link, expose is trying to connect to the SQLite database. |
@mpociot so it seems that running expose from supervisor is having this problem and it does not seem to load the right configuration file (i deleted a comma from ~/.expose/config.php to check if startup fails). When running
|
I did try to change database key from config and work when running manually, but when running in supervisor the config is ignored. |
There is no way to specify the config file as a CLI argument or --option right? |
What worked for me now: |
Can confirm, that when running with supervisord it is not working, but when starting it directly everything works as expected. I also had to change my startup command to |
same problem here. also changed my supervisor command like @goellner did. running without supervisor works ... |
I was able to solve this through these steps 1 - 2 - open the file and change database to a custom path 'database' => '/home/forge/expose-db/expose.db', 3 - run 4 - /users should work for you as expose should be able to create db file |
ended up using PM2 (https://pm2.keymetrics.io/) and everything worked right away. I created this file: |
@ahmedash95 can you share how you set it up on Forge? |
I'll write an article once I solve my last error but here is a quick recipe First, create an empty repo then create a site from this repo. once you do that ssh to your forge server and find the nginx config for that domain and change it's content to be like that https://beyondco.de/docs/expose/server/ssl . and just replace the ssh to your forge server and install expose globally
then copy the config file to home directory
modify the database path at
then run expose serve and make sure users tab is working Now everything should be fine apart from this bug I've right here |
Run it how? Via a daemon or manually? |
Happy to help! |
Hero status for @ahmedash95 |
@edalzell can you make sure the server's nginx config file has that way we are telling nginx to redirect any |
Turns out it was a DNS issue, I forgot to add the wildcard DNS entry. @ahmedash95's instructions went perfect |
Just to add to @edalzell comment, if someone has the same problem: You have to have a wildcard A record in your DNS settings: *.mydomain.com -> 123.123.123.123 (your server ip) |
I solve the issue following the @ahmedash95 instructions thank you |
server is running on Laravel Forge.
php 7.3
expose.mydomain.com, /sites and /settings is working, but when clicking the users tab, there is a 504 timeout and a generic nginx error page.
The text was updated successfully, but these errors were encountered: