Post installation problem

Hi,

I just finished installing a Kobotoolbox on my server (HTTP) and it say everything is ready with the link and username and password, i proceed to login then i create on “New” to create a new project but its just stuck there and looping then my name does not show in top right corner it just shows N/A.
I have tried to register then after entering the data i get 500 error in the next page any assistance would be much appreciated.
Thank you.

Ok i understand the error 500 when registering is caused by wrong SMTP config, i tried to update using python3 run.py --update i got this error: fatal: not a git repository (or any of the parent directories): .git

1 Like

Hi @Kal_Lam ,
thank you for your reply but it is not a solution for the loading new project loop its only an idea why the 500 error is popping up and i still have issues in the questions i posted.

Hi
I just wanted to get some additional information:

  1. Is this the first time you are installing on your own server?
  2. If No, to 1 above, have you ever seen this problem before?
  3. If Yes to 1 above, have you tried uninstalling and getting all the steps right as you may have noticed?

Stephane

1 Like

Hi stephan,
Yes it is the first time i install it on my server altho i tried multiple times eventually yesterday i reset my machine and tried from scratch, this time before i ran run.py i checked my used 80 ports and it showed tcp and tcp6 i killed the process and ran run.py and everything worked ok. but the down side is i lost my ssh connection to the machine and i could only access it via vsphere portal. it seems that it added some ip’s in the ip tables with the range on 172.22 and 23 and 28 which are already used in my network now everything works fine but i can only access the web page from specific subnets and no ssh whatsoever and it seems it created over 68 virtual adapters and added some routes.

kobo-install does not touch anything about iptables but I think docker does.

2 Likes

is there anyway i can change those ips ? or they have to come by default ? what would happen if i to remove them?

I’m pretty sure if you remove them, docker won’t work anymore.
You can take a look at this https://docs.docker.com/network/iptables/
Maybe it can help.

1 Like

thank you i will try to dig deeper into it.

1 Like

Guys is it normal for the docker to create all these ip tables ?

Generated by iptables-save v1.8.3 on Tue Jun 9 09:03:43 2020

*filter
:INPUT ACCEPT [241346:123996456]
:FORWARD DROP [0:0]
:OUTPUT ACCEPT [87579:19864899]
:DOCKER - [0:0]
:DOCKER-ISOLATION-STAGE-1 - [0:0]
:DOCKER-ISOLATION-STAGE-2 - [0:0]
:DOCKER-USER - [0:0]
-A FORWARD -j DOCKER-USER
-A FORWARD -j DOCKER-ISOLATION-STAGE-1
-A FORWARD -o br-5420aa7aa546 -m conntrack --ctstate RELATED,ESTABLISHED -j ACCEPT
-A FORWARD -o br-5420aa7aa546 -j DOCKER
-A FORWARD -i br-5420aa7aa546 ! -o br-5420aa7aa546 -j ACCEPT
-A FORWARD -i br-5420aa7aa546 -o br-5420aa7aa546 -j ACCEPT
-A FORWARD -o br-3f742c4448f4 -m conntrack --ctstate RELATED,ESTABLISHED -j ACCEPT
-A FORWARD -o br-3f742c4448f4 -j DOCKER
-A FORWARD -i br-3f742c4448f4 ! -o br-3f742c4448f4 -j ACCEPT
-A FORWARD -i br-3f742c4448f4 -o br-3f742c4448f4 -j ACCEPT
-A FORWARD -o docker0 -m conntrack --ctstate RELATED,ESTABLISHED -j ACCEPT
-A FORWARD -o docker0 -j DOCKER
-A FORWARD -i docker0 ! -o docker0 -j ACCEPT
-A FORWARD -i docker0 -o docker0 -j ACCEPT
-A DOCKER -d 172.22.0.2/32 ! -i br-5420aa7aa546 -o br-5420aa7aa546 -p tcp -m tcp --dport 80 -j ACCEPT
-A DOCKER-ISOLATION-STAGE-1 -i br-5420aa7aa546 ! -o br-5420aa7aa546 -j DOCKER-ISOLATION-STAGE-2
-A DOCKER-ISOLATION-STAGE-1 -i br-3f742c4448f4 ! -o br-3f742c4448f4 -j DOCKER-ISOLATION-STAGE-2
-A DOCKER-ISOLATION-STAGE-1 -i docker0 ! -o docker0 -j DOCKER-ISOLATION-STAGE-2
-A DOCKER-ISOLATION-STAGE-1 -j RETURN
-A DOCKER-ISOLATION-STAGE-2 -o br-5420aa7aa546 -j DROP
-A DOCKER-ISOLATION-STAGE-2 -o br-3f742c4448f4 -j DROP
-A DOCKER-ISOLATION-STAGE-2 -o docker0 -j DROP
-A DOCKER-ISOLATION-STAGE-2 -j RETURN
-A DOCKER-USER -j RETURN
COMMIT

Completed on Tue Jun 9 09:03:43 2020

Generated by iptables-save v1.8.3 on Tue Jun 9 09:03:43 2020

*nat
:PREROUTING ACCEPT [127954:8269853]
:INPUT ACCEPT [6268:935141]
:OUTPUT ACCEPT [2122:156273]
:POSTROUTING ACCEPT [122103:7353717]
:DOCKER - [0:0]
-A PREROUTING -m addrtype --dst-type LOCAL -j DOCKER
-A OUTPUT ! -d 127.0.0.0/8 -m addrtype --dst-type LOCAL -j DOCKER
-A POSTROUTING -s 172.22.0.0/16 ! -o br-5420aa7aa546 -j MASQUERADE
-A POSTROUTING -s 172.21.0.0/16 ! -o br-3f742c4448f4 -j MASQUERADE
-A POSTROUTING -s 172.18.0.0/16 ! -o docker0 -j MASQUERADE
-A POSTROUTING -s 172.22.0.2/32 -d 172.22.0.2/32 -p tcp -m tcp --dport 80 -j MASQUERADE
-A DOCKER -i br-5420aa7aa546 -j RETURN
-A DOCKER -i br-3f742c4448f4 -j RETURN
-A DOCKER -i docker0 -j RETURN
-A DOCKER ! -i br-5420aa7aa546 -p tcp -m tcp --dport 80 -j DNAT --to-destination 172.22.0.2:80
COMMIT

Completed on Tue Jun 9 09:03:43 2020