Howdy, Stranger!

It looks like you're new here. If you want to get involved, click one of these buttons!

Sign In Register

Quick Links


Categories

In this Discussion

› › After rebooting my VDS, the websites stop working
New on LowEndTalk? Please Register and read our Community Rules.

All new Registrations are manually reviewed and approved, so a short delay after registration may occur before your account becomes active.

After rebooting my VDS, the websites stop working

arnoldzarnoldz Member
in Help

After rebooting my VDS, the websites stop working
I'm using Fastpanel, could it be the cause?

Debian 12

«13

Comments

  • xvpsxvps Member

    Yes, Fastpanel is way too fast for ordinary websites.
    You should use a slower panel.

    Thanked by 16yoursunny OhJohn Decicus BasToTheMax TimboJones emgh cybertech beanman109 skorupion khalequzzaman Voltrina LordSpock Frameworks COLBYLICIOUS unsafetypin Alyx
  • EthernetServersEthernetServers Member, Patron Provider

    Can you clarify what "stop working" means?

    Any errors you can share might be help the community assist you better.

    Thanked by 3arnoldz BasToTheMax noob404
  • raviravi Member

    Check status of the services, like:
    Apache, MySQL etc.

    Thanked by 1arnoldz
  • fitkohfitkoh Member
    edited February 14

    @arnoldz said:
    After rebooting my VDS, the websites stop working
    I'm using Fastpanel, could it be the cause?

    Debian 12

    There are many possible reasons for a website to stop working.

    Are you receiving any error messages? Have you checked log files? What behavior are sites exhibiting?

    Disclaimer: I don't use fastpanel.

    Thanked by 1arnoldz
  • arnoldzarnoldz Member

    Seems like Fastpanel isn't to blame
    I restarted another one of my VPS servers with Fastpanel, and the websites continued to work just fine

  • arnoldzarnoldz Member

    @EthernetServers said:
    Can you clarify what "stop working" means?

    The sites become unavailable through the browser

  • arnoldzarnoldz Member

    @fitkoh said:

    @arnoldz said:
    After rebooting my VDS, the websites stop working
    I'm using Fastpanel, could it be the cause?

    Debian 12

    There are many possible reasons for a website to stop working.

    Are you receiving any error messages? Have you checked log files? What behavior are sites exhibiting?

    Disclaimer: I don't use fastpanel.

    The sites simply become inaccessible through the browser
    I can't tell you about any specific errors because after that, I completely reinstalled Debian and rebuilt and reconfigured all the sites from scratch (since I didn't have a backup)

  • fitkohfitkoh Member

    @arnoldz said:

    @fitkoh said:

    @arnoldz said:
    After rebooting my VDS, the websites stop working
    I'm using Fastpanel, could it be the cause?

    Debian 12

    There are many possible reasons for a website to stop working.

    Are you receiving any error messages? Have you checked log files? What behavior are sites exhibiting?

    Disclaimer: I don't use fastpanel.

    The sites simply become inaccessible through the browser
    I can't tell you about any specific errors because after that, I completely reinstalled Debian and rebuilt and reconfigured all the sites from scratch (since I didn't have a backup)

    The lack of evidence will make it very challenging to identify the problem.

    Thanked by 2arnoldz khalequzzaman
  • TheGreatOakleyTheGreatOakley Member

    Don't reboot your machine next time. Only weak minded people do reboots.

    Thanked by 10yoursunny farsighter arnoldz BasToTheMax ILikeCheapShit cybertech hyperblast khalequzzaman Frameworks COLBYLICIOUS
  • xvpsxvps Member

    @fitkoh said:

    @arnoldz said:

    @fitkoh said:

    @arnoldz said:
    After rebooting my VDS, the websites stop working
    I'm using Fastpanel, could it be the cause?

    Debian 12

    There are many possible reasons for a website to stop working.

    Are you receiving any error messages? Have you checked log files? What behavior are sites exhibiting?

    Disclaimer: I don't use fastpanel.

    The sites simply become inaccessible through the browser
    I can't tell you about any specific errors because after that, I completely reinstalled Debian and rebuilt and reconfigured all the sites from scratch (since I didn't have a backup)

    The lack of evidence will make it very challenging to identify the problem.

    The lack of skills will make it impossible to identify the problem.

    Thanked by 4TimboJones khalequzzaman skorous Alyx
  • wadhahwadhah Member

    @arnoldz said:

    I haven't always encountered such cases; this is the first time in my 28 years of using hosting that this has happened.

    PSA: This user has 28 years experience hosting websites.

    Thanked by 4xvps arnoldz khalequzzaman imok
  • yoursunnyyoursunny Member, IPv6 Advocate

    @TheGreatOakley said:
    Don't reboot your machine next time. Only weak minded people do reboots.

    True.
    We have a VDS that has not rebooted for 29 years.
    It runs snailspeedpanel for what matters.

    Thanked by 8wadhah OhJohn arnoldz BasToTheMax TimboJones khalequzzaman mustafamw3 COLBYLICIOUS
  • zedzed Member

    Sounds like you need an admin.

    Thanked by 1arnoldz
  • farsighterfarsighter Member

    Hmm...
    Maybe your firewall rules are not configured to persist after a reboot?

    Thanked by 2arnoldz noob404
  • kevindskevinds Member, LIR
    edited February 14

    @arnoldz said:
    The sites become unavailable through the browser

    Again... What does that actually mean?

    Timeout? 404 pages? 503 pages? Sites showing the code instead of rendering? 'Site not found'? Message saying Site Suspended? Message saying 'Site seized by the FBI'?

    Thanked by 3BasToTheMax arnoldz mustafamw3
  • commercialcommercial Member

    @TheGreatOakley said:
    Don't reboot your machine next time. Only weak minded people do reboots.

    So I'm a weak minded people ;)
    Please explains it :)
    I'm hunger to learn more

  • arnoldzarnoldz Member
    edited February 14

    @wadhah said:

    @arnoldz said:

    I haven't always encountered such cases; this is the first time in my 28 years of using hosting that this has happened.

    PSA: This user has 28 years experience hosting websites.

    Yes
    I've almost always used only shared hosting
    I have very little experience with VPS

  • arnoldzarnoldz Member

    This site can’t be reached
    mydomain.edu refused to connect.

  • arnoldzarnoldz Member
    edited February 14 
    **nginx**
2025/02/14 20:41:07 [emerg] 519#519: bind() to [2a0d:9ec2:0:f055::3894]:80 failed (99: Cannot assign requested address)



    **apache2**
[Fri Feb 14 09:47:09.407490 2025] [core:notice] [pid 13138:tid 13138] AH00094: Command line: '/usr/sbin/apache2'
[Fri Feb 14 20:40:55.335444 2025] [mpm_prefork:notice] [pid 13138:tid 13138] AH00170: caught SIGWINCH, shutting down gracefully
[Fri Feb 14 20:41:07.232151 2025] [suexec:notice] [pid 544:tid 544] AH01232: suEXEC mechanism enabled (wrapper: /usr/lib/apache2/suexec)
[Fri Feb 14 20:41:07.329905 2025] [mpm_prefork:notice] [pid 546:tid 546] AH00163: Apache/2.4.62 (Debian) mod_fcgid/2.3.9 mpm-itk/2.4.7-04 configured -- resuming normal operations
[Fri Feb 14 20:41:07.329934 2025] [core:notice] [pid 546:tid 546] AH00094: Command line: '/usr/sbin/apache2'
    Thanked by 1fitkoh
  • arnoldzarnoldz Member

    @kevinds said:

    @arnoldz said:
    The sites become unavailable through the browser

    Again... What does that actually mean?

    Timeout? 404 pages? 503 pages? Sites showing the code instead of rendering? 'Site not found'? Message saying Site Suspended? Message saying 'Site seized by the FBI'?

    This site can’t be reached
    mydomain.edu refused to connect.

  • TimboJonesTimboJones Member

    @arnoldz said:

    **nginx**
2025/02/14 20:41:07 [emerg] 519#519: bind() to [2a0d:9ec2:0:f055::3894]:80 failed (99: Cannot assign requested address)



    **apache2**
[Fri Feb 14 09:47:09.407490 2025] [core:notice] [pid 13138:tid 13138] AH00094: Command line: '/usr/sbin/apache2'
[Fri Feb 14 20:40:55.335444 2025] [mpm_prefork:notice] [pid 13138:tid 13138] AH00170: caught SIGWINCH, shutting down gracefully
[Fri Feb 14 20:41:07.232151 2025] [suexec:notice] [pid 544:tid 544] AH01232: suEXEC mechanism enabled (wrapper: /usr/lib/apache2/suexec)
[Fri Feb 14 20:41:07.329905 2025] [mpm_prefork:notice] [pid 546:tid 546] AH00163: Apache/2.4.62 (Debian) mod_fcgid/2.3.9 mpm-itk/2.4.7-04 configured -- resuming normal operations
[Fri Feb 14 20:41:07.329934 2025] [core:notice] [pid 546:tid 546] AH00094: Command line: '/usr/sbin/apache2'

    Sounds like you should stop apache2 and restart nginx.

    Do you even know which you should be running?

  • emghemgh Member, Megathread Squad

    Have you tried rebooting and then restarting?

    Thanked by 7davide eb1995 barbaros khalequzzaman TimboJones imok COLBYLICIOUS
  • davidedavide Member

    Thanked by 2emgh TimboJones
  • cybertechcybertech Member

    i would blame the vds provider 🤭

    Thanked by 4zed Falzo khalequzzaman COLBYLICIOUS
  • fitkohfitkoh Member

    @arnoldz said:

    **nginx**
2025/02/14 20:41:07 [emerg] 519#519: bind() to [2a0d:9ec2:0:f055::3894]:80 failed (99: Cannot assign requested address)



    **apache2**
[Fri Feb 14 09:47:09.407490 2025] [core:notice] [pid 13138:tid 13138] AH00094: Command line: '/usr/sbin/apache2'
[Fri Feb 14 20:40:55.335444 2025] [mpm_prefork:notice] [pid 13138:tid 13138] AH00170: caught SIGWINCH, shutting down gracefully
[Fri Feb 14 20:41:07.232151 2025] [suexec:notice] [pid 544:tid 544] AH01232: suEXEC mechanism enabled (wrapper: /usr/lib/apache2/suexec)
[Fri Feb 14 20:41:07.329905 2025] [mpm_prefork:notice] [pid 546:tid 546] AH00163: Apache/2.4.62 (Debian) mod_fcgid/2.3.9 mpm-itk/2.4.7-04 configured -- resuming normal operations
[Fri Feb 14 20:41:07.329934 2025] [core:notice] [pid 546:tid 546] AH00094: Command line: '/usr/sbin/apache2'

    Have you tried running your error message through a search engine?

    Thanked by 1arnoldz
  • arnoldzarnoldz Member

    @emgh said:
    Have you tried rebooting and then restarting?

    Et tu, Brute...
    Democratēs?

  • blorgedblorged Member

    Hire a sysadmin or pay for managed hosting.

  • arnoldzarnoldz Member
    edited February 15

    @fitkoh said:

    @arnoldz said:

    **nginx**
2025/02/14 20:41:07 [emerg] 519#519: bind() to [2a0d:9ec2:0:f055::3894]:80 failed (99: Cannot assign requested address)



    **apache2**
[Fri Feb 14 09:47:09.407490 2025] [core:notice] [pid 13138:tid 13138] AH00094: Command line: '/usr/sbin/apache2'
[Fri Feb 14 20:40:55.335444 2025] [mpm_prefork:notice] [pid 13138:tid 13138] AH00170: caught SIGWINCH, shutting down gracefully
[Fri Feb 14 20:41:07.232151 2025] [suexec:notice] [pid 544:tid 544] AH01232: suEXEC mechanism enabled (wrapper: /usr/lib/apache2/suexec)
[Fri Feb 14 20:41:07.329905 2025] [mpm_prefork:notice] [pid 546:tid 546] AH00163: Apache/2.4.62 (Debian) mod_fcgid/2.3.9 mpm-itk/2.4.7-04 configured -- resuming normal operations
[Fri Feb 14 20:41:07.329934 2025] [core:notice] [pid 546:tid 546] AH00094: Command line: '/usr/sbin/apache2'

    Have you tried running your error message through a search engine?

    For me, that would be 2 simple
    I'm not looking for easy ways

  • arnoldzarnoldz Member

    @cybertech said:
    i would blame the vds provider 🤭

    My hoster is so brilliant that I can't believe this is possible

  • arnoldzarnoldz Member
    edited February 15

    @blorged said:
    Hire a sysadmin or pay for managed hosting.

    Why?

    If u need, hire for urself baby 🙂 🌹

This discussion has been closed.