Search results

Hey, Alright did you try the; If not then do that check, if nothing try the first ca-certs commands again then re-try. Also, Yeah I only copy pasted the 'update-cs-certificates' section, just wanted to make sure you had that there.

@Ironeer Hmmm, You can give this a go again (bit different) for the ca-certificates issue; You can try this; See if this changes anything. Also, can you go check: /var/lib/dpkg/info/ca-certificates.postinst : and rightclick+edit, then see if it has something similar to the following...

Fair enough :) Okay's give this fella a go: Your server really is not liking the ca-certificates :P

Hey, I understand, especially when you have alot of invaluable stuff on the VPS, though I do re-call you saying it was a 'fresh install'? Anyway, let's try the following first: Then again: Let's see how this goes. Regards

@Ironeer 'apt-get install -y ca-certificates' not 'apt-get install -y update-ca-certificates' Also, just installed onto test server and everything went without a hitch using Ubuntu 17.04. Re-try with corrected above code. If this still does not work we could try a last resort thing, but, this...

I think he just missed the 's' when replying, as I did put the 's' on my command. @Ironeer Currently just setting up TeamSpeak on a new test server (as my other one doesn't seem to let me select Ubuntu 17.04.... :/ ) to see if I can replicate the errors, please bear with me. I did do the...

Hey, Did you try re-run the: --- Try this command: See if you still get errors from that and when you try to install the bot again, I am guessing it will be the same as before.

Hey, Okay until he comes back on (As he probably knows exactly what is wrong) we can try a few other things. Try: Then re-try. If it doesn't work you can try purging them: Let me know how these go.

Hey, For now do what it suggests and manually execute it then post error's here for @Qhiliqq

Hey, If you have not done yet on your VPS run the 'apt-get update' Then run 'apt-get install -y ca-certificates' Then run the 'update-ca-certificates' See if this works or not. Regards.

Hey, Can you try just 'apt-get update' and see if you receive the same error? Note that this command may take a long time as well.

What he said :) As example, with the place I have my VPS they install the 'bare minimum' and expect you to install everything yourself, most places do this. I'm lucky it is on a very fast network so it only took roughly 15 minutes or less to install the whole bot. (Bolck of the waiting was...

@Ironeer Hey, I don't think so, I moved from a CentOS server to Ubuntu by a complete backup and I had no problems. Just wondering how long you left the install on 'Installing necessary packages'? As it can take a very long time, I found that Ubuntu is extremely slow compared to CentOS. Regards.

Hey, Alrighty, glad it is working for you now and hopefully if anyone else has the same issue they now know how to fix it. Regards, Kos -BRG

@DJMaxx_ Hey, Just noticed you marked the thread as solved. Did you figure the problem out? If so could you post how/what fixed it, as this will help other's if they end up with the same problem.

@DJMaxx_ Hey, Try to install your version of the libXcomposite: https://packages.debian.org/search?searchon=contents&keywords=libXcomposite.so.1.0.0&mode=path&suite=stable&arch=any

Hey, Did you install the Bot manually or did you use the installer? Also, set your bot to log 10 and then try again then copy paste the entire log here. Edit* Also what bit is your system 32 or 64?

Update* It is a Redhat 7 Xen Virtualisation kernel bug. there is a fix to use a different kernel instead of Redhat but if I am correct SinusBot has to use Redhat correct? Thanks.

@FinnerHD You have to go into your SinusBot directory and edit the config, scroll down the bottom and add the url there, save then restart the SinusBot.

@Xuxe Hey, Thanks for the reply, That will be a little hard, I have (As stated in the Update) re-imaged the OS to Ubuntu and installed everything from there. That being said, seeing as how this is a test server (That I actually intend on moving over to due to problems with the other one plus...