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!
Heya @daee894f57454653a64eecf94c28a9,
Do you have anything listening on port 80 that can serve your website on that port?
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.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
/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:
<VirtualHost *:80>
ServerAdmin admin@example.com
DocumentRoot /var/www/dbdesigner
ServerName example.com
<Directory /var/www/dbdesigner>
AllowOverride All
Require all granted
</Directory>
ErrorLog ${APACHE_LOG_DIR}/error.log
CustomLog ${APACHE_LOG_DIR}/access.log combined
</VirtualHost>
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;
}
}
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.
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.
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.
Get paid to write technical tutorials and select a tech-focused charity to receive a matching donation.
Full documentation for every DigitalOcean product.
The Wave has everything you need to know about building a business, from raising funding to marketing your product.
Stay up to date by signing up for DigitalOcean’s Infrastructure as a Newsletter.
New accounts only. By submitting your email you agree to our Privacy Policy
Scale up as you grow — whether you're running one virtual machine or ten thousand.
Sign up and get $200 in credit for your first 60 days with DigitalOcean.*
*This promotional offer applies to new accounts only.