It may be an error in the document. I have started it according to the document, but there is no

[fre2d0m]

I successfully started the container according to this document: https://openpanel.dev/docs/self-hosting/self-hosting

docker ps It looks like this.：

But the next step can't be continued, because the 3000 port is not open. If it is deliberately designed, how should I put it behind my reverse proxy in the next step?

[lindesvard]

Good catch, since the default proxy has access to each service I never exposed any ports. You can easily fix this by adjusting your docker-compose.yml and expose 3000 for both (but one of them needs to listen on 3001 or something else.

I'll add a ticket to update the wizard to handle this and add documentation on it.

[diopisemou]

Good catch, since the default proxy has access to each service I never exposed any ports. You can easily fix this by adjusting your docker-compose.yml and expose 3000 for both (but one of them needs to listen on 3001 or something else.

I'll add a ticket to update the wizard to handle this and add documentation on it.

If you have created the ticket or have the specs ready i can contribute on that

[fre2d0m]

And what is the difference between the /api path in the dashboard and the /api path in the api service? I noticed that both services have the same /api prefix, which leads to the fact that I can only use different domain names to use dashboard and tracker api. Question mark

If my understanding is correct, then in the setup.sh link, the user needs to enter 2 domain names instead of 1. e.g. dashboard.domain.com and api.domain.com

[lindesvard]

And what is the difference between the /api path in the dashboard and the /api path in the api service? I noticed that both services have the same /api prefix, which leads to the fact that I can only use different domain names to use dashboard and tracker api. Question mark

dashboards api is just for internal health check for docker.

If my understanding is correct, then in the setup.sh link, the user needs to enter 2 domain names instead of 1. e.g. dashboard.domain.com and api.domain.com

Since you have different setup (your own proxy) everything is a bit different. Our setup only needs one domain (to make is simpler)

domain.com/api* -> Proxies everything to api domain.com/* -> Everything else goes to the dashboard

And since you (I assume) have choosen sub domains instead of one domain + sub path your setup is different from ours.

Thats why you need to provide different apiUrl etc

[fre2d0m]

Help, I need help. The deployed docker container is shown in the figure below:

If I want to create a reverse proxy as an entrance, how should I open the port correctly and configure the proxy?

The current reverse proxy is as follows:

• analytics.domain.com/api/* --> :49000
• analytics.domain.com --> :49001

[lindesvard]

Thats looks correct to me. Whats your issue exactly? What do you get when you visiting analytics.domain.com/api/ and analytics.domain.com?

Below is how our Caddy proxy looks like:

$DOMAIN_NAME {
    encode gzip
    
    handle_path /api* {
        reverse_proxy op-api:3000
    }

    reverse_proxy /* op-dashboard:3000
}