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.
This textbox defaults to using Markdown to format your answer.
You can type !ref in this text area to quickly search our full set of tutorials, documentation & marketplace offerings and insert the link!
These answers are provided by our Community. If you find them useful, show some love by clicking the heart. If you run into issues leave a comment, or add your own answer to help others.
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:
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:
For CentOS/RHEL:
3. DNS and IP Address
4. Web Server Configuration
/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.Example for Apache:
Example for Nginx:
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:
If the application works with SELinux in permissive mode, you’ll need to restore the correct contexts or adjust the policies.