Skip to main content

Internet access lost after cPanel installation

alfasoft
Hello. I installed centos 7 and then installed cpanel + whm. I had internet connection in the server, accessed it through ssh and installed the software. After installation, I was able to access whm and login, to finish configuring the installed system. After configuration, WHM requested a reboot, I pressed the reboot button, and after the server restarted, I had no internet connectivity. I am not able to access the server through SSH nor WHM, and from the server I am not able to ping any site. I am still able to access the server through IPMI. I don't know if this is something installation related or where to look for any problem during the configuration process. Any hints on how to figure this out? Thank you.

Comments

73 comments

Date Votes
  • 000
    I know there have been some issues with the ticket system log in today. Can you try logging out and logging back in to ensure you get a new session?

    I open with OTHER BROWSER!, but the problem persist: when we try CREATE NEW REQUEST: system is disabled
    0
  • cPRex Jurassic Moderator
    Can you reply to the ticket directly from the email instead of through the ticket system? That will work as well.
    0
  • 000
    Can you reply to the ticket directly from the email instead of through the ticket system? That will work as well.

    sure master!, I open from EMAIL but system not allow I reply and NOT ALLOW I create NEW ticket. The message from AARON is: but this is my folder /etc/sysconfig/network-scripts: you can see, result is: https://forums.cpanel.net/threads/after-of-install-cpanel-my-centos-dont-have-etc-sysconfig-network-scripts-ifcfg-eth0-is-dangerous.691161/ and the content of /etc/sysconfig/network-scripts/ifcfg-enp2s0 is this: #################################### DEVICE=enp2s0 ONBOOT=yes BOOTPROTO=none IPADDR=84.94.204.3 PREFIX=32 GATEWAY=84.94.204.6 DEFROUTE=yes IPV6INIT=yes IPV6ADDR=xxx/64 IPV6_DEFAULTGW=fe80::1 IPV6_DEFROUTE=yes #################################### what lines we need change? BOOTPROTO=none by BOOTPROTO=static ??? any more ??? god!, terrible experience with this installaion of cPanel . . . but excellent service from @cPRex! thanks
    0
  • cPRex Jurassic Moderator
    I'm glad to be able to help as much as I can! I would try changing it to static to see if that helps, although your hosting provider would be able to tell you the best setting available on their network. I didn't mean to try and open the ticket system link from the email, but to actually just send the reply from your email client or device as we get those messages too.
    0
  • 000
    master @cPRex then I need change only ONE line ?
    0
  • cPRex Jurassic Moderator
    Yes - to start with, I would only change the one line to see if that works well for you.
    0
  • 000
    Yes - to start with, I would only change the one line to see if that works well for you.

    just now I have:
    [root@PEPSI~]# systemctl status NetworkManager " NetworkManager.service - Network Manager Loaded: loaded (/usr/lib/systemd/system/NetworkManager.service; disabled; vendor preset: enabled) Active: inactive (dead) Docs: man:NetworkManager(8) Jun 15 15:39:29 PEPSI NetworkManager[1000]: [1623789569.8829] policy: set 'System enp2s0' (enp2s0) as default for IPv6 routing and DNS Jun 15 15:39:29 PEPSI NetworkManager[1000]: [1623789569.8829] device (enp2s0): Activation: successful, device activated. Jun 15 15:39:29 PEPSI NetworkManager[1000]: [1623789569.8834] manager: NetworkManager state is now CONNECTED_GLOBAL Jun 15 15:39:29 PEPSI NetworkManager[1000]: [1623789569.8841] manager: startup complete Jun 15 15:40:40 PEPSI systemd[1]: Stopping Network Manager... Jun 15 15:40:40 PEPSI NetworkManager[1000]: [1623789640.8992] caught SIGTERM, shutting down normally. Jun 15 15:40:40 PEPSI NetworkManager[1000]: [1623789640.8999] manager: NetworkManager state is now CONNECTED_SITE Jun 15 15:40:40 PEPSI NetworkManager[1000]: [1623789640.9686] exiting (success) Jun 15 15:40:40 PEPSI systemd[1]: NetworkManager.service: Succeeded. Jun 15 15:40:40 PEPSI systemd[1]: Stopped Network Manager. [root@PEPSI ~]#
    also I have:
    [root@PEPSI ~]# nmcli dev status Error: NetworkManager is not running. [root@PEPSI ~]#
    and finally I have: [CODE=bash]DEVICE=enp2s0 ONBOOT=yes BOOTPROTO="static" IPADDR=184.94.204.3 PREFIX=32 GATEWAY=184.94.204.6 DEFROUTE=yes IPV6INIT=yes IPV6ADDR=oh... IPv6 is detectable in many web sites::2/64 IPV6_DEFAULTGW=fe80::1 IPV6_DEFROUTE=yes
    all fine ? note: this /etc/sysconfig/network-scripts/ifcfg-enp2s0 dont have * HWADDR * NM_CONTROLLED * NETMASK
    0
  • 000
    oh... again, UNIQUE RESULT server NOT reachable and now: [CODE=sql][2021-06-15 16:17:02 -0500] [21802] ( INFO): Thank you for installing cPanel & WHM 11.96! warn [cpanel_initial_install] Could not close the file '/var/cpanel/analytics/system_id' with error: Operation not permitted Removing /root/installer.lock.
    0
  • cPRex Jurassic Moderator
    It really seems like there is an issue with the operating system itself on the provider you are using since you are getting so many odd errors. The system_id file is a unique code for your specific server to help us track the analytics, and it seems odd that something in the /var/cpanel directory would have a file operation failure. At this point we really need to examine one of the servers directly. If you are still having issues with the ticket system, can you email cs@cpanel.net so they can help you look into that? That will open a ticket directly with our Customer Service team, and then once the ticket system issues are resolved our Technical Support team can look into the install issue.
    0
  • 000
    It really seems like there is an issue with the operating system itself on the provider you are using since you are getting so many odd errors. The system_id file is a unique code for your specific server to help us track the analytics, and it seems odd that something in the /var/cpanel directory would have a file operation failure. At this point we really need to examine one of the servers directly. If you are still having issues with the ticket system, can you email cs@cpanel.net[/EMAIL] so they can help you look into that? That will open a ticket directly with our Customer Service team, and then once the ticket system issues are resolved our Technical Support team can look into the install issue.

    Thanks by your help master @cPRex yet we can"t open ticket 94335417 neither we can OPEN NEW Ticket. Then from OTHER SERVER with cPanel, we open NEW ticket: 94335671 but... can you believe this "answer" AFTER of 18 hours: cPanel THECNICAL: " I regret to hear that you are still encountering issues when rebooting your server. Please clarify precisely what you mean when you say the server is not reachable. What method are you using when you attempt to access the server? Do you receive any error messages when you attempt to access the server? Have you performed any tests to determine the server's state? Can you ping the server's main IP address? Can you connect to the SSH port? " My god!... more of 20 MESSAGES in ticket, and this answer from PROFESSIONAL THECNIC. Not even my 3 year old would answer that. NOTE: after of MORE 10 messages in post number 94335671
    0
  • cPRex Jurassic Moderator
    Can you just reply letting the tech know the server is completely offline and no one can connect to it? To test this, we may need access to one of your CentOS 8 systems so we can perform the installation on our end and see where the issue happens.
    0
  • 000
    To test this, we may need access to one of your CentOS 8 systems so we can perform the installation on our end and see where the issue happens.

    Again, thanks. I believe ONLY YOU hear/read the problem. Master @cPRex if you read the messages in 94335671 you can see YESTERDAY: 1// we install cPanel 2// we send LOGIN to cPanel 3// staff login into server, they TOUCH and then server YES REBOOT fine. 4// they NEVER say the "trick" 5// we NEED REINSTALL server 6// problems RETURN
    0
  • cPRex Jurassic Moderator
    I do see our team is able to reach the SSH port on the system that you provided access to, although we were not able to log in. If we aren't able to access the system on our end either, there won't be much troubleshooting we can do. If the system is 100% inaccessible even to SSH after the cPanel install, it sounds like there is something else happening with the networking on the machine. It would be best to get us access to one of the CentOS 8 systems before cPanel has been installed so we can do our troubleshooting with that.
    0
  • 000
    master @cCPRex yesterday: 1// we install cPanel. 2// send LOGIN to STAFF cPAnel 3// STAFF cPanel login into server by more of 4 hours (maybe running maybe NO running commands) 4// they send message "ALL is fine, restart" 5// after of REBOOT all run fine, you can see: 6// NOBODY reply the question then: YES IS POSSIBLE, but WHY cPanel NOT SAY what we need EDIT to reboot server ?
    0
  • cPRex Jurassic Moderator
    I don't think we can say what is needed because it likely isn't an issue with cPanel. Are you able to get us access to a new CentOS 8 server in your environment?
    0
  • 000
    I don't think we can say what is needed because it likely isn't an issue with cPanel. Are you able to get us access to a new CentOS 8 server in your environment?

    now by time number 25 we need REINSTALL all server, here is our last installation: master you see some error ?
    0
  • cPRex Jurassic Moderator
    Nothing on that error was helpful to me. Are you able to get us access to a new CentOS 8 server in your environment?
    0
  • 000
    offcorss, after of run
    /sbin/shutdown -r now
    again server NOT IS reachable
    0
  • cPRex Jurassic Moderator
    I still do not think this is a cPanel issue, but a problem with your environment. It would be interesting to compare the results of the network configuration on that particular system immediately after the cPanel installation, and then from a console after the failed reboot, to see if there is a change there. cPanel support would not be able to assist with that as you would need console access from your provider. The installation seems to be working well except that last error you mention, which seems to be related to the filesystem on the server itself. It would be best to get your hosting provider involved to help with these problems as we can't reboot systems on our end.
    0
  • 000
    Nothing on that error was helpful to me. Are you able to get us access to a new CentOS 8 server in your environment?

    master @cPRex now AGAIN we need REINSTALL ALL becouse connection = DEATH. Then is fine for you: we install cPanel, WE NOT REBOOT, we send ACCESS LOGIN to you ?
    0
  • cPRex Jurassic Moderator
    I don't believe reinstalling on this platform is going to help. You've reinstalled enough times to prove that is not going to work. Yes, if you could get us the access to the server after cPanel is installed but before it has been rebooted we would be happy to check the system.
    0
  • 000
    I don't believe reinstalling on this platform is going to help. You've reinstalled enough times to prove that is not going to work. Yes, if you could get us the access to the server after cPanel is installed but before it has been rebooted we would be happy to check the system.

    sure master, but please remember, 11 hours back: sorry by repeat but: in steap numer 5 all is confirmed: YES IS POSSIBLE, but nobody say HOW.
    0
  • cPRex Jurassic Moderator
    Here is what needs to happen to diagnose the issue: -perform the CentOS 8 installation -check and record the network settings -install cPanel -check and record the network settings -reboot the server, causing the issue to happen -check and record the network settings Somewhere in one of those three steps there will be a difference. This would be best performed by your host or server admin.
    0
  • 000
    oh master AGAIN: can you helpus please?
    0
  • 000
    Here is what needs to happen to diagnose the issue: -perform the CentOS 8 installation -check and record the network settings -install cPanel -check and record the network settings -reboot the server, causing the issue to happen -check and record the network settings Somewhere in one of those three steps there will be a difference. This would be best performed by your host or server admin.

    >>> -check and record the network settings how we do that? which commands we run?
    0
  • cPRex Jurassic Moderator
    At this point we really need to work through the ticket. If you aren't able to check the network settings after the install you'd have to work with your host.
    0
  • 000
    At this point we really need to work through the ticket. If you aren't able to check the network settings after the install you'd have to work with your host.

    master we can't install cPanel because cPanel BLOCK our IP
    0
  • 000
    Here is what needs to happen to diagnose the issue: -perform the CentOS 8 installation -check and record the network settings -install cPanel -check and record the network settings -reboot the server, causing the issue to happen -check and record the network settings Somewhere in one of those three steps there will be a difference. This would be best performed by your host or server admin.

    yesterday I send to you the info:
    0
  • cPRex Jurassic Moderator
    Please continue to work through the ticket.
    0
  • 000
    Please continue to work through the ticket.

    50 minutes back we reply about cPanel BLOCK our IP and nobody reply
    0

Please sign in to leave a comment.

Didn't find what you were looking for?

New post