Related

403 Forbidden using Flask, WSGI and Apache2 Question Question
how do I configure htaccess files in EACH folder I want to protect ? Question Question

Question

Apache2 Restart Problem

Posted June 26, 2017 50.2k views
ApacheDebian

So everytime i type “service apache2 restart” into putty, i get an error

apache2: Syntax error on line 268 of /etc/apache2/apache2.conf: Syntax error on line 30 of /etc/apache2/sites-enabled/000-default: Expected </Directory> but saw </VirtualHost>
Action ‘configtest’ failed.
The Apache error log may have more information.
can anyone help me?

Add a comment
k0ala
By:
k0ala

Related

403 Forbidden using Flask, WSGI and Apache2 Question Question
how do I configure htaccess files in EACH folder I want to protect ? Question Question
Add a comment
1 comment
  • bpedie September 4, 2020
    Reply Report 
    Sep 04 13:32:42 vps-65dbc114 sudo[191519]: pam_unix(sudo:session): session closed for user root
Sep 04 13:32:47 vps-65dbc114 kernel: [UFW BLOCK] IN=ens3 OUT= MAC=fa:16:3e:4d:23:f9:ee:cd:c1:81:18:88:08:00 SRC=185.153.199.187 DST=51.91.125.34>
Sep 04 13:32:57 vps-65dbc114 sudo[191565]:   ubuntu : TTY=pts/0 ; PWD=/home/ubuntu ; USER=root ; COMMAND=/usr/bin/systemctl start apache2
Sep 04 13:32:57 vps-65dbc114 sudo[191565]: pam_unix(sudo:session): session opened for user root by ubuntu(uid=0)
Sep 04 13:32:57 vps-65dbc114 systemd[1]: Starting The Apache HTTP Server...
-- Subject: A start job for unit apache2.service has begun execution
-- Defined-By: systemd
-- Support: http://www.ubuntu.com/support
-- 
-- A start job for unit apache2.service has begun execution.
-- 
-- The job identifier is 54579.
Sep 04 13:32:57 vps-65dbc114 apachectl[191583]: apache2: Syntax error on line 225 of /etc/apache2/apache2.conf: Syntax error on line 35 of /etc/>
Sep 04 13:32:57 vps-65dbc114 apachectl[191568]: Action 'start' failed.
Sep 04 13:32:57 vps-65dbc114 apachectl[191568]: The Apache error log may have more information.
Sep 04 13:32:57 vps-65dbc114 systemd[1]: apache2.service: Control process exited, code=exited, status=1/FAILURE
-- Subject: Unit process exited
-- Defined-By: systemd
-- Support: http://www.ubuntu.com/support
-- 
-- An ExecStart= process belonging to unit apache2.service has exited.
-- 
-- The process' exit code is 'exited' and its exit status is 1.
Sep 04 13:32:57 vps-65dbc114 systemd[1]: apache2.service: Failed with result 'exit-code'.
-- Subject: Unit failed
-- Defined-By: systemd
-- Support: http://www.ubuntu.com/support
-- 
-- The unit apache2.service has entered the 'failed' state with result 'exit-code'.
Sep 04 13:32:57 vps-65dbc114 systemd[1]: Failed to start The Apache HTTP Server.
-- Subject: A start job for unit apache2.service has failed
-- Defined-By: systemd
-- Support: http://www.ubuntu.com/support
-- 
-- A start job for unit apache2.service has finished with a failure.
-- 
-- The job identifier is 54579 and the job result is failed.
Sep 04 13:32:57 vps-65dbc114 sudo[191565]: pam_unix(sudo:session): session closed for user root
Sep 04 13:33:03 vps-65dbc114 kernel: [UFW BLOCK] IN=ens3 OUT= MAC=fa:16:3e:4d:23:f9:ee:cd:c1:81:18:88:08:00 SRC=178.32.228.195 DST=51.91.125.34 >
Sep 04 13:33:04 vps-65dbc114 kernel: [UFW BLOCK] IN=ens3 OUT= MAC=fa:16:3e:4d:23:f9:ee:cd:c1:81:18:88:08:00 SRC=178.32.228.195 DST=51.91.125.34 >
Sep 04 13:33:06 vps-65dbc114 kernel: [UFW BLOCK] IN=ens3 OUT= MAC=fa:16:3e:4d:23:f9:ee:cd:c1:81:18:88:08:00 SRC=178.32.228.195 DST=51.91.125.34 >
Sep 04 13:33:10 vps-65dbc114 kernel: [UFW BLOCK] IN=ens3 OUT= MAC=fa:16:3e:4d:23:f9:ee:cd:c1:81:18:88:08:00 SRC=178.32.228.195 DST=51.91.125.34 >
Sep 04 13:33:16 vps-65dbc114 kernel: [UFW BLOCK] IN=ens3 OUT= MAC=fa:16:3e:4d:23:f9:ee:cd:c1:81:18:88:08:00 SRC=45.129.33.12 DST=51.91.125.34 LE>
Sep 04 13:33:18 vps-65dbc114 kernel: [UFW BLOCK] IN=ens3 OUT= MAC=fa:16:3e:4d:23:f9:ee:cd:c1:81:18:88:08:00 SRC=178.32.228.195 DST=51.91.125.34 >
Sep 04 13:33:22 vps-65dbc114 kernel: [UFW BLOCK] IN=ens3 OUT= MAC=fa:16:3e:4d:23:f9:ee:cd:c1:81:18:88:08:00 SRC=94.102.51.28 DST=51.91.125.34 LE>
Sep 04 13:33:26 vps-65dbc114 sshd[191590]: Received disconnect from 222.186.30.112 port 31892:11:  [preauth]
Sep 04 13:33:26 vps-65dbc114 sshd[191590]: Disconnected from 222.186.30.112 port 31892 [preauth]
Sep 04 13:33:38 vps-65dbc114 kernel: [UFW BLOCK] IN=ens3 OUT= MAC=fa:16:3e:4d:23:f9:ee:cd:c1:81:18:88:08:00 SRC=45.129.33.82 DST=51.91.125.34 LE>
Sep 04 13:33:38 vps-65dbc114 kernel: [UFW BLOCK] IN=ens3 OUT= MAC=fa:16:3e:4d:23:f9:ee:cd:c1:81:18:88:08:00 SRC=185.175.93.24 DST=51.91.125.34 L>
Sep 04 13:33:43 vps-65dbc114 sshd[191592]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=112.85.42.73 >
Sep 04 13:33:45 vps-65dbc114 sshd[191592]: Failed password for root from 112.85.42.73 port 61953 ssh2
Sep 04 13:33:48 vps-65dbc114 sshd[191592]: Failed password for root from 112.85.42.73 port 61953 ssh2
Sep 04 13:33:50 vps-65dbc114 sshd[191592]: Failed password for root from 112.85.42.73 port 61953 ssh2
Sep 04 13:33:53 vps-65dbc114 sshd[191592]: Received disconnect from 112.85.42.73 port 61953:11:  [preauth]
Sep 04 13:33:53 vps-65dbc114 sshd[191592]: Disconnected from authenticating user root 112.85.42.73 port 61953 [preauth]
Sep 04 13:33:53 vps-65dbc114 sshd[191592]: PAM 2 more authentication failures; logname= uid=0 euid=0 tty=ssh ruser= rhost=112.85.42.73  user=root
Sep 04 13:34:07 vps-65dbc114 kernel: [UFW BLOCK] IN=ens3 OUT= MAC=fa:16:3e:4d:23:f9:ee:cd:c1:81:18:88:08:00 SRC=110.25.93.42 DST=51.91.125.34 LE>
Sep 04 13:34:08 vps-65dbc114 kernel: [UFW BLOCK] IN=ens3 OUT= MAC=fa:16:3e:4d:23:f9:ee:cd:c1:81:18:88:08:00 SRC=45.129.33.82 DST=51.91.125.34 LE>
Sep 04 13:34:08 vps-65dbc114 kernel: [UFW BLOCK] IN=ens3 OUT= MAC=fa:16:3e:4d:23:f9:ee:cd:c1:81:18:88:08:00 SRC=112.78.187.83 DST=51.91.125.34 L>
Sep 04 13:34:18 vps-65dbc114 kernel: [UFW BLOCK] IN=ens3 OUT= MAC=fa:16:3e:4d:23:f9:ee:cd:c1:81:18:88:08:00 SRC=45.129.33.151 DST=51.91.125.34 L>
Sep 04 13:34:32 vps-65dbc114 kernel: [UFW BLOCK] IN=ens3 OUT= MAC=fa:16:3e:4d:23:f9:ee:cd:c1:81:18:88:08:00 SRC=45.129.33.152 DST=51.91.125.34 L>
Sep 04 13:34:56 vps-65dbc114 kernel: [UFW BLOCK] IN=ens3 OUT= MAC=fa:16:3e:4d:23:f9:ee:cd:c1:81:18:88:08:00 SRC=74.82.47.2 DST=51.91.125.34 LEN=>
Sep 04 13:35:15 vps-65dbc114 sudo[191595]:   ubuntu : TTY=pts/0 ; PWD=/home/ubuntu ; USER=root ; COMMAND=/usr/sbin/ufw desable
Sep 04 13:35:15 vps-65dbc114 sudo[191595]: pam_unix(sudo:session): session opened for user root by ubuntu(uid=0)
Sep 04 13:35:15 vps-65dbc114 sudo[191595]: pam_unix(sudo:session): session closed for user root
Sep 04 13:35:15 vps-65dbc114 kernel: [UFW BLOCK] IN=ens3 OUT= MAC=fa:16:3e:4d:23:f9:ee:cd:c1:81:18:88:08:00 SRC=185.176.27.174 DST=51.91.125.34 >
Sep 04 13:35:35 vps-65dbc114 sshd[191597]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=112.85.42.73 >
Sep 04 13:35:36 vps-65dbc114 kernel: [UFW BLOCK] IN=ens3 OUT= MAC=fa:16:3e:4d:23:f9:ee:cd:c1:81:18:88:08:00 SRC=210.14.96.118 DST=51.91.125.34 L>
Sep 04 13:35:37 vps-65dbc114 sshd[191597]: Failed password for root from 112.85.42.73 port 19211 ssh2
Sep 04 13:35:39 vps-65dbc114 sshd[191597]: Failed password for root from 112.85.42.73 port 19211 ssh2
Sep 04 13:35:43 vps-65dbc114 sshd[191597]: Failed password for root from 112.85.42.73 port 19211 ssh2
Sep 04 13:35:43 vps-65dbc114 sshd[191597]: Received disconnect from 112.85.42.73 port 19211:11:  [preauth]
Sep 04 13:35:43 vps-65dbc114 sshd[191597]: Disconnected from authenticating user root 112.85.42.73 port 19211 [preauth]
Sep 04 13:35:43 vps-65dbc114 sshd[191597]: PAM 2 more authentication failures; logname= uid=0 euid=0 tty=ssh ruser= rhost=112.85.42.73  user=root
Sep 04 13:35:57 vps-65dbc114 sudo[191599]:   ubuntu : TTY=pts/0 ; PWD=/home/ubuntu ; USER=root ; COMMAND=/usr/sbin/ufw disable
Sep 04 13:35:57 vps-65dbc114 sudo[191599]: pam_unix(sudo:session): session opened for user root by ubuntu(uid=0)
Sep 04 13:35:57 vps-65dbc114 sudo[191599]: pam_unix(sudo:session): session closed for user root
    edited by MattIPv4

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.

×
Submit an Answer
8 answers
hansen June 26, 2017

Hi @k0ala
Can you post the file here /etc/apache2/sites-enabled/000-default ?

Reply Report
  • k0ala June 26, 2017

    I don’t think so? I’m on file zilla and whatever I try to do to the 000-default folder it says

    Error: Directory /etc/apache2/sites-available/default: no such file or directory
    Error: Failed to retrieve directory listing

    Reply Report
    • k0ala June 26, 2017

      If I try to download or enter the folder, it says that ^^

      Reply Report
      • hansen June 26, 2017

        @k0ala
        In PuTTY, simply write this command:

        cat /etc/apache2/sites-enabled/000-default

        And then copy-and-paste the content here - you might need to scroll a little to get everything.
        And please use the </> button in the comment editor to make sure it doesn’t lose formatting.

        Reply Report
        • k0ala June 26, 2017 
          <VirtualHost *:80>
        ServerAdmin webmaster@localhost

        DocumentRoot /var/www
        <Directory />
                Options FollowSymLinks
                AllowOverride None      </Directory>
        <Directory /var/www/>
                Options Indexes FollowSymLinks MultiViews
                AllowOverride All
                Order allow,deny
                allow from all
        </Directory>

        ScriptAlias /cgi-bin/ /usr/lib/cgi-bin/
        <Directory "/usr/lib/cgi-bin">
                AllowOverride None
                Options +ExecCGI -MultiViews +SymLinksIfOwnerMatch
                Order allow,deny
                Allow from all
        </Directory>

        ErrorLog ${APACHE_LOG_DIR}/error.log

        # Possible values include: debug, info, notice, warn, error, crit,
        # alert, emerg.
        LogLevel warn

        CustomLog ${APACHE_LOG_DIR}/access.log combined
</VirtualHost>
          Reply Report
        • pk46066 February 10, 2021

          sudo a2enmod rewrite

          service apache2 restart

          Reply Report
k0ala June 26, 2017
[deleted]
Reply Report
hansen June 26, 2017

@k0ala Just starting a new thread, since it was getting a little narrow.

My guess would be that this is your problem:

        <Directory />
                Options FollowSymLinks
                AllowOverride None      </Directory>

Which should look like this:

        <Directory />
                Options FollowSymLinks
                AllowOverride None
        </Directory>

But I don’t understand why it says line 30 in the error, when this is clearly not line 30.
Anyways, let’s edit the file with this command to make it look like the above:

nano /etc/apache2/sites-enabled/000-default

When you are done editing, hold CTRL key and press X key, release keys, press Y key and press Enter key.

Now restart Apache service apache2 restart.

Reply Report
  • k0ala June 26, 2017

    thank you so much!

    Reply Report
  • k0ala June 26, 2017

    Ok well now when i restart apache it says
    “service apache2 restart
    [ ok ] Restarting web server: apache2 … waiting .”

    Reply Report
    • hansen June 26, 2017

      Run this command to show the last 20 lines from the error log:

      tail -20 /var/log/apache2/error.log
      Reply Report
      • k0ala June 26, 2017 
        [Mon Jun 26 01:09:50 2017] [error] [client 23.250.117.178] script '/var/www/proxy.php' not found or unable to stat, referer: RefererString
[Mon Jun 26 01:13:50 2017] [error] [client 178.165.89.97] script '/var/www/proxy.php' not found or unable to stat, referer: RefererString
[Mon Jun 26 01:14:17 2017] [notice] caught SIGTERM, shutting down
PHP Deprecated:  Comments starting with '#' are deprecated in /etc/php5/apache2/conf.d/ming.ini on line 1 in Unknown on line 0
[Mon Jun 26 01:14:18 2017] [notice] Apache/2.2.22 (Debian) PHP/5.4.45-0+deb7u8 configured -- resuming normal operations
[Mon Jun 26 01:14:36 2017] [alert] [client 91.230.47.3] /var/www/.htaccess: Invalid command 'RewriteEngine', perhaps misspelled or defined by a module not included in the server configuration
[Mon Jun 26 01:14:58 2017] [alert] [client 208.91.115.10] /var/www/.htaccess: Invalid command 'RewriteEngine', perhaps misspelled or defined by a module not included in the server configuration
[Mon Jun 26 01:15:29 2017] [alert] [client 176.112.8.181] /var/www/.htaccess: Invalid command 'RewriteEngine', perhaps misspelled or defined by a module not included in the server configuration, referer: RefererString
[Mon Jun 26 01:15:47 2017] [notice] caught SIGTERM, shutting down
PHP Deprecated:  Comments starting with '#' are deprecated in /etc/php5/apache2/conf.d/ming.ini on line 1 in Unknown on line 0
[Mon Jun 26 01:15:48 2017] [notice] Apache/2.2.22 (Debian) PHP/5.4.45-0+deb7u8 configured -- resuming normal operations
[Mon Jun 26 01:19:05 2017] [alert] [client 46.161.9.32] /var/www/.htaccess: Invalid command 'RewriteEngine', perhaps misspelled or defined by a module not included in the server configuration
[Mon Jun 26 01:19:09 2017] [alert] [client 115.28.167.101] /var/www/.htaccess: Invalid command 'RewriteEngine', perhaps misspelled or defined by a module not included in the server configuration
[Mon Jun 26 01:21:00 2017] [alert] [client 93.179.68.158] /var/www/.htaccess: Invalid command 'RewriteEngine', perhaps misspelled or defined by a module not included in the server configuration
[Mon Jun 26 01:21:12 2017] [notice] caught SIGTERM, shutting down
PHP Deprecated:  Comments starting with '#' are deprecated in /etc/php5/apache2/conf.d/ming.ini on line 1 in Unknown on line 0
[Mon Jun 26 01:21:12 2017] [notice] Apache/2.2.22 (Debian) PHP/5.4.45-0+deb7u8 configured -- resuming normal operations
[Mon Jun 26 01:22:31 2017] [notice] caught SIGTERM, shutting down
PHP Deprecated:  Comments starting with '#' are deprecated in /etc/php5/apache2/conf.d/ming.ini on line 1 in Unknown on line 0
[Mon Jun 26 01:22:32 2017] [notice] Apache/2.2.22 (Debian) PHP/5.4.45-0+deb7u8 configured -- resuming normal operations
        Reply Report
hansen June 26, 2017

@k0ala Getting a little narrow again, so starting a new thread

Can you remove or rename the file /var/www/.htaccess, which might be the reason.
Rename command mv /var/www/.htaccess /var/www/.htaccess-OLD

Reply Report
  • k0ala June 26, 2017

    So should i run the command? Or should i remove .htaccess

    Reply Report
    • hansen June 26, 2017

      If you remove it, you should have it in a backup somewhere. If you move it, you still have it available.

      By the way, I would highly recommend that you hire a system administrator to update your server, since you are running a very old version of Apache and PHP, which has received several critical security updates since. And my guess is everything else on the server is also outdated.

      Reply Report
hansen June 26, 2017

@k0ala
What are you confused by?
The file? Do you have a backup of the file, then remove it. If not, then simply rename it.
The server? Hire a system administrator to help you with the server.

Reply Report
  • k0ala June 26, 2017

    So if I rename it(and what do i rename it to?), what will it do and will it help me run the restart apache? I’m new to this if you couldn’t tell

    Reply Report
    • hansen June 26, 2017

      @k0ala
      I have no idea what you’re trying to run on your web server, so I don’t know the consequence of removing the file, but it’s generating errors, so it doesn’t work currently.

      What have you done to the server lately, since everything stopped working - and the configuration files has been edited?

      Run this:

      mv /var/www/.htaccess /var/www/.htaccess-OLD

apache2ctl configtest

apache2ctl restart
      Reply Report
      • k0ala June 26, 2017

        mv /var/www/.htaccess /var/www/.htaccess-OLD

        mv: cannot stat `/var/www/.htaccess': No such file or directory

        apache2ctl configtest

        Syntax OK

        apache2ctl restart
        nothing happens ^

        Reply Report
hansen June 26, 2017

@k0ala
Okay, then you’ve just renamed or removed the file.
Try running the following:

service apache2 start

service apache2 status
#press Q to exit the status dialog
Reply Report
k0ala June 26, 2017

sorry for leaving @hansen, I was really tired and i went to bed… anyway

the site isn’t working and even after doing everything you said and then typing “service apache2 restart” it still said waiting, and I’m following a tutorial that requires you to type that command in order for the website to work… or else you get a 404 error and that’s exactly what’s happenening so no the site doesn’t work :/

Reply Report
k0ala June 26, 2017

I looked up some issues online and reinstalled things and it worked, my website was working. But now comes another issue which I don’t think is a droplet issue but everytime I type “node site.js” I get this long error


[2017-06-26 15:54:00.991] [INFO] [default] - DB Connection ID: 399
[2017-06-26 15:54:00.994] [INFO] [default] - DB Connection ID: 400
[2017-06-26 15:54:00.995] [INFO] [default] - DB Connection ID: 401
[2017-06-26 15:54:00.997] [INFO] [default] - DB Connection ID: 402
[2017-06-26 15:54:01.002] [TRACE] [default] - Roll 4263
[2017-06-26 15:54:01.003] [TRACE] [default] - Sucesfully updated history
[2017-06-26 15:54:01.004] [WARN] [default] - Loaded hashd8b710dfa2c8a3d990ca1dc7                                                                                           cc0a91754ac20aa6139fb7f6d44b58ee31ece8dc
[2017-06-26 15:54:01.134] [WARN] [default] - Loaded fresh prices
[2017-06-26 15:54:01.190] [WARN] [default] - Prices loaded from cache
[2017-06-26 15:54:03.934] [TRACE] [default] - Strange error
[2017-06-26 15:54:03.935] [DEBUG] [default] - { Error: listen EADDRINUSE :::8080
    at Object.exports._errnoException (util.js:1026:11)
    at exports._exceptionWithHostPort (util.js:1049:20)
    at Server.setupListenHandle [as _listen2] (net.js:1305:14)
    at listenInCluster (net.js:1353:12)
    at Server.listen (net.js:1453:7)
    at Server.listen.Server.attach (/home/bot/node_modules/socket.io/lib/index.j                                                                                           s:237:9)
    at Timeout._onTimeout (/home/bot/site.js:618:29)
    at ontimeout (timers.js:488:11)
    at tryOnTimeout (timers.js:323:5)
    at Timer.listOnTimeout (timers.js:283:5)
  code: 'EADDRINUSE',
  errno: 'EADDRINUSE',
  syscall: 'listen',
  address: '::',
  port: 8080 }

It was working literally 10 minutes ago and now it doesn’t work

Reply Report
  • hansen June 26, 2017

    @k0ala
    It says { Error: listen EADDRINUSE :::8080, which in English would mean “error, address is already in use”.
    So you got something else running on port :::8080 - try to restart the server, since there can sometimes be lingering processes when updating.

    Reply Report
    • k0ala June 26, 2017

      Sorry for late reply again. I rebooted the server and the error is still showing up

      Reply Report
      • hansen June 26, 2017

        @k0ala
        I would recommend that create a new droplet - you can use the One-Click App called “NodeJS 6.11.0 on 16.04” and then you are up and running in seconds.
        We can continue to try to fix every single part of the current server, but it really needs a major overhaul and it would be far easier for you to setup a new droplet and copy all your data to that.

        Reply Report

Related

Looking for something else?

Ask a new question Search for more help