504 Timeout when trying to open expose.mydomain.com/users

[goellner]

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.

[mpociot]

Can you try modifying the database configuration key?
Also, try and see if the database file exists.

When clicking the user link, expose is trying to connect to the SQLite database.

[filipac]

@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 /usr/bin/php /home/forge/.composer/vendor/bin/expose serve from forge user it works as expected, it even fails if i delete that comma (loads the ~/.expose/config.php file). Any idea why supervisor might be broken? Here is my config:

directory=/home/forge
command=/usr/bin/php /home/forge/.composer/vendor/bin/expose serve local.filipac.net
numprocs=1
autostart=true
autorestart=true
user=forge

[filipac]

I did try to change database key from config and work when running manually, but when running in supervisor the config is ignored.

[filipac]

There is no way to specify the config file as a CLI argument or --option right?

[filipac]

What worked for me now: ln -s .expose/config.php .expose.php in /home/forge as that is the working directory for supervisord

[goellner]

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 command=/usr/bin/php /home/forge/.composer/vendor/bin/expose serve mydomain.com

[dasraab]

same problem here. also changed my supervisor command like @goellner did. running without supervisor works ...

[ahmedash95]

I was able to solve this through these steps

1 - $COMPOSER/vendor/beyondcode/expose/condig/expose.php to home directory -in my case- /home/forge/.expose.php

2 - open the file and change database to a custom path

'database' => '/home/forge/expose-db/expose.db',

3 - run expose serve

4 - /users should work for you as expose should be able to create db file

[goellner]

ended up using PM2 (https://pm2.keymetrics.io/) and everything worked right away. I created this file: /home/forge/.expose.php

[edalzell]

@ahmedash95 can you share how you set it up on Forge?

[ahmedash95]

@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 /location part as Forge taking care of all other stuff

ssh to your forge server and install expose globally

composer global require beyondcode/expose

then copy the config file to home directory

 cp /home/forge/.config/composer/vendor/beyondcode/expose/config/expose.php /home/forge/.expose.php

modify the database path at.expose.php like below (make sure expose-db directory exists as expose will not create it)

'database' => '/home/forge/expose-db/expose.db',

then run expose serve and make sure users tab is working

Now everything should be fine apart from this bug I've right here
#31

[edalzell]

Run it how? Via a daemon or manually?

[ahmedash95]

Run it how? Via a daemon or manually?

as you want. can be manually like

/home/forge/.config/composer/vendor/bin/expose serve share.yourdomain.com --port 8085

or daemon using forge. but make sure to set the path to home directory

[SamuelNitsche]

Run it how? Via a daemon or manually?

as you want. can be manually like

/home/forge/.config/composer/vendor/bin/expose serve share.yourdomain.com --port 8085

or daemon using forge. but make sure to set the path to home directory

Yep, that works. Thank you!

[ahmedash95]

Happy to help!

[edalzell]

Hero status for @ahmedash95

[edalzell]

I still cannot get it to work, how frustrating. I have installed it locally in my Forge site: (composer require...).

I have this in /home/forge:

And it is reading the config file (I had a typo in there the first time and got an error).

I have this in my nginx conf:

    location / {
        proxy_pass             http://127.0.0.1:8080;
        proxy_read_timeout     60;
        proxy_connect_timeout  60;
        proxy_redirect         off;

        # Allow the use of websockets
        proxy_http_version 1.1;
        proxy_set_header Upgrade $http_upgrade;
        proxy_set_header Connection 'upgrade';
        proxy_set_header Host $host;
        proxy_cache_bypass $http_upgrade;
    }

I have SSL on w/ wildcards:

When I go to my expose url I get

But I can't get to the admin page nor any share, even though the share seems to work.

Lastly my config:

    'admin' => [
        'database' => '/home/forge/.expose/expose.db',
        'subdomain' => 'admin',

So, what silly thing did I miss?

[ahmedash95]

@edalzell can you make sure the server's nginx config file has . as prefix of server name

that way we are telling nginx to redirect any subdomain.(your expose domain) to expose so you can get the proper response

[edalzell]

Turns out it was a DNS issue, I forgot to add the wildcard DNS entry. @ahmedash95's instructions went perfect

[goellner]

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)

[enzolarosa]

I solve the issue following the @ahmedash95 instructions

thank you