Install database design tool in linux server can’t access from other machine

Question

Hi all. I new in server configuration. I am was install database design tool online from dynobird at https://github.com/didin1453fatih/dbdesigner.id This project was inactive, but i need install this to my server.

The backend was install and server was run at port 80.

When i call from my browser with ip address i can’t access this application. but when i try to hit local using curl localhost it was return html file text.

KFSys · Answer

Heya @daee894f57454653a64eecf94c28a9 , Do you have anything listening on port 80 that can serve your website on that port? 1. Check Server Configuration First, ensure that your server is configured to listen on the appropriate port (port 80, as you mentioned) and that the application is correctly set up to serve content on that port. You can check this by: Looking into the configuration files of your application. Ensure the port is set to 80. Checking if the server is running by executing a command like sudo netstat -tuln | grep :80 on Linux. This will show if your server is listening on port 80. 2. Firewall Settings The server’s firewall may be blocking incoming connections on port 80. You’ll need to allow traffic on that port: For Ubuntu/Debian: sudo ufw allow 80 sudo ufw reload For CentOS/RHEL: sudo firewall-cmd --permanent --add-port=80/tcp sudo firewall-cmd --reload 3. DNS and IP Address Direct IP Access : Make sure you are using the correct IP address to access your server. If the IP address is correct and you still can’t access it, there could be a network issue or misconfiguration. DNS Settings : If you’re using a domain name, ensure that the DNS records are correctly pointing to your server’s IP address. This might not be applicable if you are using the IP address directly. 4. Web Server Configuration If you are using a web server like Apache or Nginx, make sure that it is configured to serve your application. Check the configuration files (/etc/apache2/sites-available/ for Apache or /etc/nginx/sites-available/ for Nginx) to see if there is a server block or virtual host set up for your application. Ensure that the document root in the web server configuration points to the directory where your application is installed. Example for Apache: ServerAdmin admin@example.com DocumentRoot /var/www/dbdesigner ServerName example.com AllowOverride All Require all granted ErrorLog ${APACHE_LOG_DIR}/error.log CustomLog ${APACHE_LOG_DIR}/access.log combined Example for Nginx: server { listen 80; server_name example.com; root /var/www/dbdesigner; index index.html index.htm; location / { try_files $uri $uri/ =404; } } 5. Check Application Logs Look at the application logs for any errors that might indicate what the problem is. This could provide clues if there’s an issue with the application itself not starting up or encountering errors when attempting to serve content. 6. Browser Cache Sometimes, an old or corrupted cache can cause issues accessing newly set up sites. Try clearing your browser’s cache or accessing the site from an incognito window or a different browser. 7. SELinux Contexts (If applicable) If you are on a server where SELinux is enabled, ensure that the correct contexts are set for the web files. You can temporarily set SELinux to permissive mode to see if it’s causing the access issue: sudo setenforce 0 If the application works with SELinux in permissive mode, you’ll need to restore the correct contexts or adjust the policies.