as you did the installation, could you give me more details about the domains thanks.
1 Like
Hi @juanda159
Welcome to the community forum. Could you please provide specific details of the problem you are encountering when installing so that other users can chime in to support. Normallly when a user provides as much detail as possible, it makes it easy for others to provide specific support,
Regards
Stephane
1 Like
When executing kobotoolbox it gives me the error shown in the image of bakos resources, could you give me more information about how to configure the domains?
I think I’d use this thread for my very basic question. Is it a good idea to install KoBo on a tiny Ubuntu VPS (10 GB storage, 1 GB RAM) with http://fastpanel.direct control panel installed and a simple personal website hosted on it? Or should I go for a faster VPS with more storage? Thanks!
Hi @patjoshea,
Welcome to the community! Kindly please be informed that we have a support article Installing KoBoToolbox on Your Own Servers which should guide you on the requirements while installing KoBoToolbox on your own server.
Have a great day!
Hello @patjoshea,
Based on a lot of problems documented here using own server installations, it might be preferable to use one of the two the KoBo servers first when you start working with KoBoToolbox.
1 Like
Does this installation allow to use kobocollect with my own server? and how can you do it? Can I also add users? I did the installation but did not allow me to do any of these steps
Hi,
Is this the first time you had installed Kobo on your own servers? If so, I suggest that you retry the process on your need and see how it works for you.
Stephane
I tried again, the redis database still fails, for which I think kobocollect does not work correctly, the error is the following Redis connection to 127.0.0.1:6379 failed - connect ECONNREFUSED
I’d appreciate your help .
Juan
hi dear
i have probleme i see this qouistion multi
Wait for another 600 seconds?
i using fixed Os ubunto 18 with 8G Ram And 1 Tera HHD and CPU core i5 10th
hi @abdojkl! I also have the exact same screen now. Were you able to make any more progress after this?
Hi guys! My installation is stuck at this point. I am trying on a Ubuntu 18.04 LTS with 8 GB ram.
kc.mydomain.com, ee.mydomain.com and kf.mydomain.com are also working but mydomain.com is not working. Does anyone have any idea as to what might be the issue?
Hi dear
No i can’t solve this problim yet i am writing the reply .
If you speak arabic send to REMOVED PHONE NUMBER
@ramiz please don’t tag people en masse like this. Supporting people’s private installations of KoBo is not our central mission, and we try our best to help only as time permits. If that’s not enough, you can post on the job board and hire a professional to help you.
Could clarify the problem? KoBoToolbox only serves three hostnames: KPI, KoBoCAT, and Enketo Express—the ones you say are working—and if you want a fourth domain (the base mydomain.com), you need to arrange for that separately. For example, our public instance runs on kf.kobotoolbox.org (KPI), kc.kobotoolbox.org (KoBoCAT), and ee.kobotoolbox.org (Enketo Express). The root domain kobotoolbox.org is hosted by GitHub Pages, completely separately from the KoBoToolbox application.
2 Likes
I don’t see any errors. Maybe there’s a DNS problem, or an issue with KoBoCAT or Enketo Express (their logs are not visible in the screenshot). What happens if you try to visit each of KPI, KoBoCAT, and Enketo Express in a browser? Usually these will be kf.yourdomain.org, kc.yourdomain.org, and ee.yourdomain.org, but it depends on what you chose when you first ran the run.py setup.
1 Like
Hi! Sorry for tagging people, The problem has been solved. I’ll write about it in the next comment
2 Likes
I was making two mistakes here:
- I was giving full subdomain address instead of just the subdomain. So for example, instead of writing “kf” I was writing “kf.mydomain.com”
- I was running it with the root user
Fixed these two and it started running with http.
Now my next step is to run it with https. There I get stuck. Now none of my subdomains work. In the logs I see this:
The setup just keeps on running infinitely (until I stop it) without any error. This is what I see:
My server’s port 443 is open. When I try to open https://kf.mydomain.com/ it keeps on running and after some time, I get 504 timed out error from nginx. What could I be doing wrong?
1 Like
Run docker ps and see whether the containers are up? Check the container logs too.
504 for me gets solved when I restart the containers.
1 Like
I tried docker ps. The cotnainers seem to be all running except nginx:1.15-alpine. But there is another Nginx container that is running
