Jump to content
SolusVM Community


  • Content count

  • Joined

  • Last visited

  • Days Won


yourweb last won the day on May 22 2017

yourweb had the most liked content!

About yourweb

  • Rank
    Senior Member


  • Company
  1. Solusvm Whmcs client reload OS

    The default module does not have a feature like that. Instead, you will need to use a module of modulesgarden. See https://docs.whmcs.com/SolusVM: “The client also has an array of functions and statistics from within the client area, including, reboot, boot, shutdown, change passwords, change hostname, view resource usage and graphs, plus the added bonus of a serial console or VNC.”
  2. Issues with WHMCS module

    Looks like it is unable to connect to the specific port or else you would have a http status code. Did you change the port of the SolusVM install by any chance? . Can you run wget with the correct URL on the WHMCS server? In that case you will need to update this as well with the following in the Acces Hash field (replace with your HTTPS port): <port>443</port> wget https://mvmm22.test:5656/api/admin/command.php
  3. CentOS 7 KVM node issues with Windows Guests

    Did you try by any chance the cirrus driver? We do not run Windows VMs, however I have had this on a test setup before.
  4. Solus and network connection

    This is in a situation with OpenVZ, right? This is how OpenVZ works. I am not exactly sure how it is implemented in OpenVZ, but in networking terms the router knows which IP belongs to which mac address. Every packet from the router to the server is routed by mac address. As this is known by the switches and any bridging, it will direct the package to the right port and/or server. If you want to have a second IP, simply use venet0:0. veth1 will point to a second nic, which you probably do not have. Only when you use OpenVZ, the master can act as a host (aka node). However, in the situation of KVM and Xen, the master will just be the master and not run any virtual machine on it. But if you want to understand the difference between master and slave: the master is where the SolusVM control panel runs, the slave only listens to commands from the control panel. This is possible and you can do this by simply adding extra IP's to the VPS. There are many OSes. Actually, 5.3 is not supported anymore so you should not use that. Check out http://tdn.solusvm.com for more templates.
  5. VPS not installed on Slave

    Did you synchronise the templates on the slaves? And can you send the build log? See http://pic.filehostserver.eu/view/90141/
  6. ssh key access to container

    Hi Krissteel, Unfortunately this is not possible with SolusVM. You can add the keys as a regular Linux machine, just add the public key to .ssh/authorized_keys and set the correct 600 permission.
  7. Bridge

    Can you explain how this breaks your server? You should install SolusVM on a clean installed CentOS server without anything else on it. On a default installation it should not break your server. However, it is possible to configure the bridge incorrect which leaves the server unreachable after restarting the network services.
  8. After update error 500

    I advice to open a ticket since it is an urgent issue. That said, you can always checkout the logs for errors. Ps I recommend to change to nginx: https://documentation.solusvm.com/display/DOCS/NGINX+for+SolusVM+1.x?src=contextnavpagetreemode
  9. SolusVM Database

    Hi Zulqarnain, You can access the MySQL database and create your own API to access it via the webserver. The database login credentials can be found using this article: https://documentation.solusvm.com/display/DOCS/Moving+the+SolusVM+Master(check paragraph 4).
  10. Missing files.

    When you run the updated via cli you will get a bunch of errors, which is normal. As far as I can see the errors you have posted are normal.
  11. Master SolusVM, problem with slave

    Hi Xdr, The slave is a bit dumb. It only acts when it receives a command from the master. Only the master knows all the details about the VM and what actually runs on the server. Unfortunately, since you have reinstalled the master, this data is gone. Luckily for you SolusVM features an import mode which can import the VM to your panel. See https://documentation.solusvm.com/display/DOCS/Importing+Virtual+Servers+into+SolusVMfor more information? Did you change the masters IP? Update /usr/local/solusvm/data/allow.dat with the new IP on every slave.
  12. Did you reboot the server after installing? Sometimes not everything is launched properly.
  13. Issues during Trial

    Hi mrbrowning, Are you running Xen, KVM or OpenVZ? It is likely that you are not running the correct kernel, causing the VPS not to boot. Daniel
  14. Users panel login credentials

    Hi Ninet, When you go to clients, you can manage clients from there. It is not possible to retrieve the password as it is encrypted, however you can configure a new password and send that one to the user.
  15. OpenVZ restore but not seen in GUI

    Hi Ninet, SolusVM is not aware of the new VM since it is not created via SolusVM. Check this how you can import a container into SolusVM: https://documentation.solusvm.com/pages/viewpage.action?pageId=558019