Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

error 500 after installing the API on Ubuntu server 16.04 #41

Closed
F2210 opened this issue Mar 16, 2017 · 11 comments
Closed

error 500 after installing the API on Ubuntu server 16.04 #41

F2210 opened this issue Mar 16, 2017 · 11 comments

Comments

@F2210
Copy link

F2210 commented Mar 16, 2017

after successfully installing the API-key. The website asks me to click on the Check connection button. I do this but after doing this I get to see error 500 in my web browser. I tried to reinstall the connect program a few times, I did a full re-installation of my server. All of it just didn't help at all. I keep getting the error. I also checked whether the docker, BCD or BCD-proxy properly installed on it's own. the BCD and BCD-proxy do BUT. If I do apt-get install docker after installing the API-key. It gives me the message

Reading package lists... Done Building dependency tree Reading state information... Done The following NEW packages will be installed: docker 0 upgraded, 1 newly installed, 0 to remove and 0 not upgraded. Need to get 0 B/12.2 kB of archives. After this operation, 65.5 kB of additional disk space will be used. Selecting previously unselected package docker. (Reading database ... 92231 files and directories currently installed.) Preparing to unpack .../docker_1.5-1_amd64.deb ... Unpacking docker (1.5-1) ... Processing triggers for man-db (2.7.5-1) ... Setting up docker (1.5-1) ...

which is weird because you would think docker was installed with the API-key. After finding out about this I reinstalled again but with a docker re installment before the installment of the API-key. Which unfortunately didn't help...

I hope there is actually a solution to this. Prior to all of this I actually managed to get your service running but I uninstalled it back then (2 days ago) because I thought it would interfere with programs that were already installed at that moment. So I did a re-installation, installed bytesized API-key, the service gave me the 500 error. reinstalled API-key a few times using the uninstallation method provided on your site:

apt-get remove docker service bcd stop service bcd-proxy stop rm /usr/local/bin/bcd && rm /usr/local/bin/bcd-proxy && rm /lib/systemd/system/bcd.service && rm /lib/systemd/system/bcd-proxy.service

reinstalled the system after that and now I can't manage to install it again. Please help me because I did have the privilege to use your system litterally a day ago. But now I just can't manage to use it again and that is really a miss.

I could really use some help so please. Help everyone by helping me!

@F2210
Copy link
Author

F2210 commented Mar 16, 2017

the code inserted in the text message, resupplied properly
first number of lines:
apt-get remove docker service bcd stop service bcd-proxy stop rm /usr/local/bin/bcd && rm /usr/local/bin/bcd-proxy && rm /lib/systemd/system/bcd.service && rm /lib/systemd/system/bcd-proxy.service

second number of lines:
Reading package lists... Done Building dependency tree Reading state information... Done The following NEW packages will be installed: docker 0 upgraded, 1 newly installed, 0 to remove and 13 not upgraded. Need to get 12.8 kB of archives. After this operation, 42.0 kB of additional disk space will be used. Get:1 http://ftp2.nluug.nl/os/Linux/distr/kali kali-rolling/main amd64 docker amd64 1.5-1+b1 [12.8 kB] Fetched 12.8 kB in 0s (14.0 kB/s) Selecting previously unselected package docker. (Reading database ... 453692 files and directories currently installed.) Preparing to unpack .../docker_1.5-1+b1_amd64.deb ... Unpacking docker (1.5-1+b1) ... Processing triggers for menu (2.1.47+b1) ... Processing triggers for man-db (2.7.6.1-2) ... Setting up docker (1.5-1+b1) ... Processing triggers for menu (2.1.47+b1) ...

@maran
Copy link

maran commented Mar 17, 2017

Can you please confirm you are using Ubuntu 14.04 or 16.04. These are the only supported by the automatic installation script.

@F2210
Copy link
Author

F2210 commented Mar 17, 2017 via email

@maran
Copy link

maran commented Mar 18, 2017

Could you tell me your Bytesized username and the output of cat /etc/lsb-release and uname -a and cat /proc/cpuinfo?

@F2210
Copy link
Author

F2210 commented Mar 18, 2017 via email

@F2210
Copy link
Author

F2210 commented Mar 19, 2017 via email

@maran
Copy link

maran commented Mar 20, 2017

You did not give me your Bytesized Username yet. Let me know and I will check it out.

@F2210
Copy link
Author

F2210 commented Mar 20, 2017 via email

@F2210
Copy link
Author

F2210 commented Mar 20, 2017 via email

@maran
Copy link

maran commented Mar 20, 2017

Some device on route from my website to your home server is refusing the connection.

Either XS4All is blocking the connection on purpose or your router/firewall is blocking it. Both traceroutes as any connection to port 8112 is being actively blocked.

I've updated the website to not give you an generic error anymore but tell you a bit more about the actual problem so others won't bang their heads against this.

@maran maran closed this as completed Mar 20, 2017
@F2210
Copy link
Author

F2210 commented Mar 20, 2017 via email

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants