galexrt / docker-sinusbot

Docker container for the famous TeamSpeak 3 SinusBot by Michael Friese.
MIT License
25 stars 13 forks source link

Docker image isnt still working #42

Closed prodingerA closed 6 years ago

prodingerA commented 6 years ago

I updated the image and restartet the sinusbot but i isnt still working :D in docker logs is this:

Checking if scripts directory is empty => Scripts directory is marked, scripts were already copied. Nothing to do. -> No /sinusbot/config/config.ini found, not linking. => Starting SinusBot (https://sinusbot.com) by Michael Friese ... _ ___ BETA / | | | | | | / | )/ _ | _ | || .` | || _ \ \ () || | |/||_|_/|//\/ |_|

Version: 0.14.3-0e747fd (C) 2013-2018 Michael Friese. All rights reserved.

2018/08/19 22:13:06 X [MAIN] Starting up fake x-server... 2018/08/19 22:13:06 [GENERAL/SCRIPTS] INFO Loading ScriptPlugin advertising.js 2018/08/19 22:13:06 [GENERAL/SCRIPTS] INFO Loading ScriptPlugin alonemode.js 2018/08/19 22:13:06 [GENERAL/SCRIPTS] INFO Loading ScriptPlugin bookmark.js 2018/08/19 22:13:06 [GENERAL/SCRIPTS] INFO Loading ScriptPlugin followme.js 2018/08/19 22:13:06 [GENERAL/SCRIPTS] INFO Loading ScriptPlugin norecording.js 2018/08/19 22:13:06 [GENERAL/SCRIPTS] INFO Loading ScriptPlugin rememberChannel.js 2018/08/19 22:13:06 [GENERAL/SCRIPTS] INFO Loading ScriptPlugin welcome.js could not contact update server

It is the same error before and in docker ps it isnt showing up

galexrt commented 6 years ago

@Scuddix I'm unable to reproduce the error. Are you sure your server can reach the Sinusbot website as stated in forum posts about this issue?

prodingerA commented 6 years ago

I have reinstalled the note twiced but couldnt get to any soloution. I also couldnt reproduce this error on a other server. I think the update server just blocked my IP :D But If you are a nice person and promise to not damage my server i can provide login credentials So you can fix the bug.

galexrt commented 6 years ago

@Scuddix You have to reach out to the Sinusbot.com admins/makers to ask them for your IP to be unbanned. This is nothing I have in control.

Closing as this is not a problem with the Docker image in this case.