Fixed the config for domain #50
Open
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
I was facing issue in deploying tiledesk with domain. The config file was wrong. I have edited the config file. so domain appears.
Setting up Nginx Reverse Proxy with SSL for Tiledesk
This configuration allows you to serve the Tiledesk dashboard securely over HTTPS, while the backend continues to run on its default Docker port (8081). It also automatically redirects HTTP traffic to HTTPS.
1️⃣ Prerequisites
Tiledesk running on localhost:8081 (Docker container)
Domain pointing to your server, e.g., tile.megaversepro.app
Nginx installed on your server
Certbot installed for Let’s Encrypt SSL certificates
2️⃣ Nginx Configuration
Create or edit your Nginx site config, e.g., /etc/nginx/sites-available/tile.megaversepro.app:
Redirect all HTTP traffic to HTTPS
server {
listen 80;
server_name tile.megaversepro.app;
}
HTTPS server
server {
listen 443 ssl http2;
server_name domain.com;
}
3️⃣ Apply Configuration
Test Nginx config
sudo nginx -t
Reload Nginx to apply changes
sudo systemctl reload nginx