• Register
1 vote
90 views

Problem :

I am facing the problem which I am trying to fix from the couple of days now and still I don't know what should I do, I am searching for answers but all of those I came across are of no use to me.

I am very new here and I am really hopeful that someone can resolve my issue.

Below is my error message :

$ systemctl status nginx.service
nginx.service - Startup script for nginx service
Loaded: loaded (/usr/lib/systemd/system/nginx.service; enabled; vendor preset: disabled)
Active: failed (Result: exit-code) since Sun 2019-12-29 13:23:35 GMT; 2min 20s ago
6 5 3
7,540 points

Please log in or register to answer this question.

1 Answer

0 votes

Solution :

I had the same issue and tried all the solutions which I knew, and neither of them worked actually after long research I found the solution for the error as below:

You need to change your port to some other port number as the existing  80 port is already in use somewhere

You can check the available port using below command :

vi /etc/nginx/sites-available/default

Change the port by below procedure:

listen 8080 default_server;
listen [::]:8080 default_server;

After changing your port then you need to restart your nginx server with below commands:

nginx -t
service nginx restart

 

After restarting your server you will find that all your issues are resolved.

9 7 4
38,600 points

Related questions

0 votes
1 answer 96 views
96 views
Problem : I got below problem which I am trying to fix from the few days now and I am unable to know what should I do, I am looking for the answers but all of those which I found are of no use for me. I am very new here so I really hope that somebody can help me in resolving my error $ ... ------------ f...e) Jan 05 13:23:33 startdedicated.com nginx[8315]: nginx: [emerg] bind() to ----- f...e)
asked Jan 6, 2020 alecxe 7.5k points
0 votes
1 answer 216 views
216 views
Problem : I have installed the fresh copy of the Centos 7. Then I just restarted Apache but my Apache failed to start. I am stuck with the bellow error from past 5 days. Even my support could not figure out the below error. sudo service httpd start Failed to ... could not bind to address 85.25.12.20:xx Jan 04 16:08:02 startdedicated.de httpd[5710]: no listening sockets available, shutting down
asked Jan 10, 2020 alecxe 7.5k points
0 votes
2 answers 510 views
510 views
Problem : I am trying to restart my apache from terminal using the following command: sudo service apache2 restart But when executing above command I am facing below error: Job for apache2.service failed. See "systemctl status apache2.service" and "journalctl -xe" for ... AH00489: Apache/2.4.12 (Unix) configured -- resuming normal operations AH00094: Command line: '/usr/local/apache2/bin/httpd'
asked Dec 18, 2019 alecxe 7.5k points
0 votes
1 answer 2 views
2 views
Problem: I can't seem to find a solution; could you please help me “Httpd.service: control process exited, code=exited status=1”?
asked Apr 1 rakib1 51.5k points
0 votes
1 answer 2 views
2 views
Problem: Please help me to solve it out : nginx server_name_in_redirect
asked 4 days ago tuhin1 48.4k points
0 votes
1 answer 2 views
2 views
Problem: Please help me fix this dilemma: nginx proxy_max_temp_file_size
asked 4 days ago tuhin1 48.4k points
0 votes
1 answer 6 views
6 views
Problem: 414 request-uri too large nginx. How to solve this error..
asked Mar 21 charles mathews 5.5k points
0 votes
1 answer 995 views
995 views
Problem : My Environment is Nginx + uwsgi and I am very new to it. I am getting a 502 bad gateway error from Nginx on certain GET requests. It seems to be related to a length of URL.. Please find below the nginx/error.log [error] 22113#0: *1 recv ... response header from upstream, client: 192.168.1.100, server: server.domain.com, request: "GET <long_url_here>" Can somebody solve this issue?
asked Nov 27, 2019 alecxe 7.5k points
0 votes
1 answer 6 views
6 views
Problem: Anyone knows about this error so please tell me .. no python application found check your startup logs for errors
asked Apr 2 Ifra 24.4k points
1 vote
1 answer 6 views
6 views
Problem: Is some body here to tell me why I am getting this warning? You configured http(80) on the standard https(443) port!.
asked Mar 26 PkGuy 13.1k points