Docker KoBoToolbox behind reverse proxy server with SSL support

Dear Jake

Thanks for great support to enable me the kobo in test environment. Now I am facing the problem SSL certificate integration with kobo toolbox in production environment( kobo server on Esx(i) in DMZ )

I have configured the Global DNS with the following sub domains:

  1. kobo.myorg.org (do’nt mention the actual DNS)

  2. kc.myorg.org

  3. ee. myorg.org

SSL certificate from Godadday

My question are :

  1. For each sub-domain we need the chained/bundle certificate, if yes, so I have concatenate the certificate in one file(ssl.crt) and create one private key file (ssl.key) and put in secrets folder of kobo docker as mentioned on github.

  2. Will i put the configurations for sub-domains and location of certificates in nginx_site_https_conf.tmpl . Well I am attaching this file with this. Please correct if there is any mistake.

I also attaching other configuration files with screen shots. Please help me , because I have deadline till Monday.

Regards,

Kaleem

docker-compose.server.yml (7.76 KB)

nginx_site_https.conf-2.tmpl (5.01 KB)

···

On Sat, Jun 24, 2017 at 7:45 PM, jpstaub jpst...@gmail.com wrote:

Hello Kaleem,

No changes should be required in jwilder/nginx-proxy. See attached docker-compose file for what I use to start a jwilder/nginx-proxy container.

To eliminate potential port conflict problems stop all containers that are not part of the KoBoToolbox deployment.

Also, to ensure the Ubuntu server firewall is not creating problems disable the firewall during deployment troubleshooting efforts.

Regards,
Jake

On Tuesday, June 20, 2017 at 6:50:49 AM UTC-4, Kaleem Qureshi wrote:

Thanks Jake, When we run the jwilder/nginx and kobo toolbox, then error comes "driver failed programming external connectivity kobo docker nginx jwilder* . I think port conflict problem. please let me that is there any change needed in docker-compose.yml file in nginx/jwilder .

Regards,
kaleem

On Thursday, June 8, 2017 at 5:48:47 PM UTC+5, jpstaub wrote:

Good morning Kaleem,

One more thing, I have login from super user , working fine . but when I create the user with djang adminsitration. User can not create the form and deploy the project?

It sounds like you have not set User permissions correctly for the user in question. On Django site administration see:
Home >> Authentication and Authorization >> Users >> User of Interest >> Permissions (Check Active) >> User permissions (select required permission for User of Interest).

Regards,
Jake

You received this message because you are subscribed to a topic in the Google Groups “Kobo Users” group.

To unsubscribe from this topic, visit https://groups.google.com/d/topic/kobo-users/kh8QEkLzVGI/unsubscribe.

To unsubscribe from this group and all its topics, send an email to kobo-users+unsubscribe@googlegroups.com.

To post to this group, send email to kobo-...@googlegroups.com.

Visit this group at https://groups.google.com/group/kobo-users.

For more options, visit https://groups.google.com/d/optout.

With Best Regards,
Kaleem Ahmad Qureshi

Regional ICT Infrastructure Engineer South Asia Region

***Country Office Pakistan, ***

Islamic Relief World Wide UK ,

Cell: 92 300 8521825 , 92 333 5135815.

Good morning Kaleem,

The method that I developed to implement SSL makes use of Let’s Encrypt certificates that are automatically generated and maintained by the LetsEncrypt companion container for nginx-proxy. By trying to use GoDaddy certificates you are attempting to mix my method with the method implemented by the KoboToolbox developers. You cannot use both at the same time. You either need to implement my method from start to finish or abandon it entirely in order to set up a working KoboToolbox deployment. If you want to use the method implemented by the KoboToolbox developers you must seek their support. I have no experience with their method and as a result cannot offer support.

Three files are attached that should help you implement my method if you would like to continue down that path.

  1. docker-compose.yml – This file is what I use to start jwilder/nginx-proxy and jrcs/letsencrypt-nginx-proxy-companion. This combination of containers is what provides reverse proxy and SSL support to a KoboToolbox instance.
  2. docker-compose.server.yml – This file is what I use to start a KoboToolbox instance. I have modified the file to reflect the domain names that you listed as examples. The only settings you should ever change are under: nginx >> environment >> VIRTUAL_HOST / LETSENCRYPT_HOST / LETSENCRYPT_EMAIL. Do not change any other settings.
  3. envfile.server.txt – This file is what holds domain and security settings. I have modified the file to reflect the domain names that you listed as examples. You need to provide your own security settings according to the directions given in the file. When you change domain names in this file you must also change the domain names in docker-compose.server.yml.
    With the three attached files you have everything you need to deploy a KoboToolbox instance with self generated and maintained SSL certificates presuming your server is publicly accessible at the domain name you are using. You can see a working example that was produced using the three files at kobo.ripcordengineering.com. Note: you cannot register a new account because I have disabled account registration.

If you cannot successfully deploy KoboToolbox but still need your own instance I am available on a professional basis.

Regards,
Jake

docker-compose.server.yml (8.44 KB)

docker-compose.yml (795 Bytes)

envfile.server.txt (1.13 KB)

···

On Friday, July 7, 2017 at 10:59:57 AM UTC-4, Kaleem Qureshi wrote:

Dear Jake

Thanks for great support to enable me the kobo in test environment. Now I am facing the problem SSL certificate integration with kobo toolbox in production environment( kobo server on Esx(i) in DMZ )

I have configured the Global DNS with the following sub domains:

  1. kobo.myorg.org (do’nt mention the actual DNS)
  1. kc.myorg.org
  1. ee. myorg.org

SSL certificate from Godadday

My question are :

  1. For each sub-domain we need the chained/bundle certificate, if yes, so I have concatenate the certificate in one file(ssl.crt) and create one private key file (ssl.key) and put in secrets folder of kobo docker as mentioned on github.
  1. Will i put the configurations for sub-domains and location of certificates in nginx_site_https_conf.tmpl . Well I am attaching this file with this. Please correct if there is any mistake.

I also attaching other configuration files with screen shots. Please help me , because I have deadline till Monday.

Regards,

Kaleem

1 Like

Thanks Jake. but no error comes after docker-compose up. But one last thing I want to confirm that for auto letsencrypt certificate we have to configure the certbot…

Regards,

Kaleem

···

On Sunday, July 9, 2017 at 6:35:12 PM UTC+5, jpstaub wrote:

Good morning Kaleem,

The method that I developed to implement SSL makes use of Let’s Encrypt certificates that are automatically generated and maintained by the LetsEncrypt companion container for nginx-proxy. By trying to use GoDaddy certificates you are attempting to mix my method with the method implemented by the KoboToolbox developers. You cannot use both at the same time. You either need to implement my method from start to finish or abandon it entirely in order to set up a working KoboToolbox deployment. If you want to use the method implemented by the KoboToolbox developers you must seek their support. I have no experience with their method and as a result cannot offer support.

Three files are attached that should help you implement my method if you would like to continue down that path.

  1. docker-compose.yml – This file is what I use to start jwilder/nginx-proxy and jrcs/letsencrypt-nginx-proxy-companion. This combination of containers is what provides reverse proxy and SSL support to a KoboToolbox instance.
  2. docker-compose.server.yml – This file is what I use to start a KoboToolbox instance. I have modified the file to reflect the domain names that you listed as examples. The only settings you should ever change are under: nginx >> environment >> VIRTUAL_HOST / LETSENCRYPT_HOST / LETSENCRYPT_EMAIL. Do not change any other settings.
  3. envfile.server.txt – This file is what holds domain and security settings. I have modified the file to reflect the domain names that you listed as examples. You need to provide your own security settings according to the directions given in the file. When you change domain names in this file you must also change the domain names in docker-compose.server.yml.
    With the three attached files you have everything you need to deploy a KoboToolbox instance with self generated and maintained SSL certificates presuming your server is publicly accessible at the domain name you are using. You can see a working example that was produced using the three files at kobo.ripcordengineering.com. Note: you cannot register a new account because I have disabled account registration.

If you cannot successfully deploy KoboToolbox but still need your own instance I am available on a professional basis.

Regards,
Jake

On Friday, July 7, 2017 at 10:59:57 AM UTC-4, Kaleem Qureshi wrote:

Dear Jake

Thanks for great support to enable me the kobo in test environment. Now I am facing the problem SSL certificate integration with kobo toolbox in production environment( kobo server on Esx(i) in DMZ )

I have configured the Global DNS with the following sub domains:

  1. kobo.myorg.org (do’nt mention the actual DNS)
  1. kc.myorg.org
  1. ee. myorg.org

SSL certificate from Godadday

My question are :

  1. For each sub-domain we need the chained/bundle certificate, if yes, so I have concatenate the certificate in one file(ssl.crt) and create one private key file (ssl.key) and put in secrets folder of kobo docker as mentioned on github.
  1. Will i put the configurations for sub-domains and location of certificates in nginx_site_https_conf.tmpl . Well I am attaching this file with this. Please correct if there is any mistake.

I also attaching other configuration files with screen shots. Please help me , because I have deadline till Monday.

Regards,

Kaleem

It works perfectly with HTTP only on LAN and no error generate after docker-compose with nginx-proxy and letsencrypt container . But main theme is that it work on https. Is there any certificates needed from letsencrpt for kobo.myorg.org ee.myorg.org kc.myorg.org or we have to configure the certbot

···

On Tuesday, July 11, 2017 at 4:04:22 PM UTC+5, Kaleem Qureshi wrote:

Thanks Jake. but no error comes after docker-compose up. But one last thing I want to confirm that for auto letsencrypt certificate we have to configure the certbot…

Regards,

Kaleem

On Sunday, July 9, 2017 at 6:35:12 PM UTC+5, jpstaub wrote:

Good morning Kaleem,

The method that I developed to implement SSL makes use of Let’s Encrypt certificates that are automatically generated and maintained by the LetsEncrypt companion container for nginx-proxy. By trying to use GoDaddy certificates you are attempting to mix my method with the method implemented by the KoboToolbox developers. You cannot use both at the same time. You either need to implement my method from start to finish or abandon it entirely in order to set up a working KoboToolbox deployment. If you want to use the method implemented by the KoboToolbox developers you must seek their support. I have no experience with their method and as a result cannot offer support.

Three files are attached that should help you implement my method if you would like to continue down that path.

  1. docker-compose.yml – This file is what I use to start jwilder/nginx-proxy and jrcs/letsencrypt-nginx-proxy-companion. This combination of containers is what provides reverse proxy and SSL support to a KoboToolbox instance.
  2. docker-compose.server.yml – This file is what I use to start a KoboToolbox instance. I have modified the file to reflect the domain names that you listed as examples. The only settings you should ever change are under: nginx >> environment >> VIRTUAL_HOST / LETSENCRYPT_HOST / LETSENCRYPT_EMAIL. Do not change any other settings.
  3. envfile.server.txt – This file is what holds domain and security settings. I have modified the file to reflect the domain names that you listed as examples. You need to provide your own security settings according to the directions given in the file. When you change domain names in this file you must also change the domain names in docker-compose.server.yml.
    With the three attached files you have everything you need to deploy a KoboToolbox instance with self generated and maintained SSL certificates presuming your server is publicly accessible at the domain name you are using. You can see a working example that was produced using the three files at kobo.ripcordengineering.com. Note: you cannot register a new account because I have disabled account registration.

If you cannot successfully deploy KoboToolbox but still need your own instance I am available on a professional basis.

Regards,
Jake

On Friday, July 7, 2017 at 10:59:57 AM UTC-4, Kaleem Qureshi wrote:

Dear Jake

Thanks for great support to enable me the kobo in test environment. Now I am facing the problem SSL certificate integration with kobo toolbox in production environment( kobo server on Esx(i) in DMZ )

I have configured the Global DNS with the following sub domains:

  1. kobo.myorg.org (do’nt mention the actual DNS)
  1. kc.myorg.org
  1. ee. myorg.org

SSL certificate from Godadday

My question are :

  1. For each sub-domain we need the chained/bundle certificate, if yes, so I have concatenate the certificate in one file(ssl.crt) and create one private key file (ssl.key) and put in secrets folder of kobo docker as mentioned on github.
  1. Will i put the configurations for sub-domains and location of certificates in nginx_site_https_conf.tmpl . Well I am attaching this file with this. Please correct if there is any mistake.

I also attaching other configuration files with screen shots. Please help me , because I have deadline till Monday.

Regards,

Kaleem

Dear Jake

Please share you skype id or whats app id to discuss it professionally.

My skype id is kaleemqureshi1 and whatsapp +923008521825

···

On Sun, Jul 9, 2017 at 6:35 PM, jpstaub jpst...@gmail.com wrote:

Good morning Kaleem,

The method that I developed to implement SSL makes use of Let’s Encrypt certificates that are automatically generated and maintained by the LetsEncrypt companion container for nginx-proxy. By trying to use GoDaddy certificates you are attempting to mix my method with the method implemented by the KoboToolbox developers. You cannot use both at the same time. You either need to implement my method from start to finish or abandon it entirely in order to set up a working KoboToolbox deployment. If you want to use the method implemented by the KoboToolbox developers you must seek their support. I have no experience with their method and as a result cannot offer support.

Three files are attached that should help you implement my method if you would like to continue down that path.

  1. docker-compose.yml – This file is what I use to start jwilder/nginx-proxy and jrcs/letsencrypt-nginx-proxy-companion. This combination of containers is what provides reverse proxy and SSL support to a KoboToolbox instance.
  2. docker-compose.server.yml – This file is what I use to start a KoboToolbox instance. I have modified the file to reflect the domain names that you listed as examples. The only settings you should ever change are under: nginx >> environment >> VIRTUAL_HOST / LETSENCRYPT_HOST / LETSENCRYPT_EMAIL. Do not change any other settings.
  3. envfile.server.txt – This file is what holds domain and security settings. I have modified the file to reflect the domain names that you listed as examples. You need to provide your own security settings according to the directions given in the file. When you change domain names in this file you must also change the domain names in docker-compose.server.yml.
    With the three attached files you have everything you need to deploy a KoboToolbox instance with self generated and maintained SSL certificates presuming your server is publicly accessible at the domain name you are using. You can see a working example that was produced using the three files at kobo.ripcordengineering.com. Note: you cannot register a new account because I have disabled account registration.

If you cannot successfully deploy KoboToolbox but still need your own instance I am available on a professional basis.

Regards,
Jake

On Friday, July 7, 2017 at 10:59:57 AM UTC-4, Kaleem Qureshi wrote:

Dear Jake

Thanks for great support to enable me the kobo in test environment. Now I am facing the problem SSL certificate integration with kobo toolbox in production environment( kobo server on Esx(i) in DMZ )

I have configured the Global DNS with the following sub domains:

  1. kobo.myorg.org (do’nt mention the actual DNS)
  1. kc.myorg.org
  1. ee. myorg.org

SSL certificate from Godadday

My question are :

  1. For each sub-domain we need the chained/bundle certificate, if yes, so I have concatenate the certificate in one file(ssl.crt) and create one private key file (ssl.key) and put in secrets folder of kobo docker as mentioned on github.
  1. Will i put the configurations for sub-domains and location of certificates in nginx_site_https_conf.tmpl . Well I am attaching this file with this. Please correct if there is any mistake.

I also attaching other configuration files with screen shots. Please help me , because I have deadline till Monday.

Regards,

Kaleem

You received this message because you are subscribed to a topic in the Google Groups “Kobo Users” group.

To unsubscribe from this topic, visit https://groups.google.com/d/topic/kobo-users/kh8QEkLzVGI/unsubscribe.

To unsubscribe from this group and all its topics, send an email to kobo-users+unsubscribe@googlegroups.com.

To post to this group, send email to kobo-...@googlegroups.com.

Visit this group at https://groups.google.com/group/kobo-users.

For more options, visit https://groups.google.com/d/optout.

With Best Regards,
Kaleem Ahmad Qureshi

Regional ICT Infrastructure Engineer South Asia Region

***Country Office Pakistan, ***

Islamic Relief World Wide UK ,

Cell: 92 300 8521825 , 92 333 5135815.

1 Like

Hi Jake,

I’m a new member in this forum as well as on this topic and will really need your help to install and configure kobotoolbox on my local computer as proof of concept. Here is my email address gee...@hotmail.com. Please let me hear from you so we can discuss further privately on this on how to help us achieve our goal by using your process. We have attempted twice trying to install this application but now. Urgent please.

Thanks,

Joe

···

On Tuesday, November 8, 2016 at 11:11:56 PM UTC-5, jpstaub wrote:

WARNING! - Use this information at your own risk. I am not a web developer. I am not a data security specialist. I am a guy making open source software work through determination rather than fundamental understanding.

This an informational post that describes a method to run a Docker KoBoToolbox instance behind a reverse proxy server with SSL support. The method set up in the included files supports either http or http access to KoBoToolbox using one domain name. Currently it does not support alias domains since the domain name and its implementation is bound up in the mechanization of kobotoolbox_nginx. From a technical standpoint, there is no reason why alias domains could not be incorporated. It hasn’t been done here more for time considerations than anything else.

Q1: Why bother with the additional complexity of a reverse proxy?
A1: Click here to read all about it.

Q2: If SSL is so good why is it such a pain in the ass to implement?
A2: I have no idea. Fortunately, there are people in this world that believe in helping a brother/sister out.

Background:
Docker-KoBoToolbox is a great way to get up and running on a Docker host that isn’t being used for much other than KoboToolbox. My problem was that I am using a Docker host for a bunch of services including other web servers. Also, I prefer to give the services I run domain names so other people can interact with them. And when a service is meant for the web, I prefer to secure it with SSL. That’s why I use jwilder/nginx-proxy (reverse proxy) combined with docker-letsencrypt-nginx-proxy-companion (letsencrypt).

Unfortunately, Docker-KoBoToolbox, neither local or server versions, is set up to run behind a reverse proxy . Additionally, the way to use domain names is by using the server version. But the server version doesn’t appear to work without an SSL certificate. For people that work with SSL certificates regularly that’s probably not a big deal. For me it’s a pain in the ass especially if all I want to do is run the service on the LAN. Plus, self signed certificates these days give browsers massive chest pains even if you manage to create them by painstakingly following all the poorly contrived instructions on the web.

Solution:
In general, the solution amounted to hijacking “docker-compose.server.yml” and “nginx_site_https.conf.tmpl” for my own purposes. “docker-compose.server.yml” was modified to make kobotoolbox_nginx compatible with the reverse proxy & letsencrypt combo. “nginx_site_https.conf.tmpl” was stripped down so kobotoolbox_nginx acts as an http server only. This way, KoBoToolbox can be run locally as an http service using domain names. KoBoToolbox can also be run over the web as an https service with a trusted certificate provided and updated automagically by letsencrypt. The modified “docker-compose.server.yml” allows for the quick & easy configuration of KoBoToolbox to run either locally (http) or over the web (https).

To implement the solution:

  • Prerequisites - 1. jwilder/nginx-proxy 2. docker-letsencrypt-nginx-proxy-companion. Both containers should be up prior to starting KoBoToolbox.
  • Configure “envfile.server.txt” with the domain and subdomain names of choice.
  • Swap out “docker-compose.server.yml” and “nginx_site_https.conf.tmpl” with the attached files.
  • Configure “docker-compose.server.yml” for http or https and the domain and subdomain names of choice.
  • Give it a try and troubleshoot as required.
  • Do others a solid and post additional information/solutions.
    Todo:
  • Implement domain alias
  • Implement domain/subdomain variables within “docker-compose.server.yml” to take advantage of settings in “envfile.server.txt”

Regards,

Jake

1 Like

Are you available now

···

On 24 Jun 2017 7:45 pm, “jpstaub” jpst...@gmail.com wrote:

Hello Kaleem,

No changes should be required in jwilder/nginx-proxy. See attached docker-compose file for what I use to start a jwilder/nginx-proxy container.

To eliminate potential port conflict problems stop all containers that are not part of the KoBoToolbox deployment.

Also, to ensure the Ubuntu server firewall is not creating problems disable the firewall during deployment troubleshooting efforts.

Regards,
Jake

On Tuesday, June 20, 2017 at 6:50:49 AM UTC-4, Kaleem Qureshi wrote:

Thanks Jake, When we run the jwilder/nginx and kobo toolbox, then error comes "driver failed programming external connectivity kobo docker nginx jwilder* . I think port conflict problem. please let me that is there any change needed in docker-compose.yml file in nginx/jwilder .

Regards,
kaleem

On Thursday, June 8, 2017 at 5:48:47 PM UTC+5, jpstaub wrote:

Good morning Kaleem,

One more thing, I have login from super user , working fine . but when I create the user with djang adminsitration. User can not create the form and deploy the project?

It sounds like you have not set User permissions correctly for the user in question. On Django site administration see:
Home >> Authentication and Authorization >> Users >> User of Interest >> Permissions (Check Active) >> User permissions (select required permission for User of Interest).

Regards,
Jake

You received this message because you are subscribed to a topic in the Google Groups “Kobo Users” group.

To unsubscribe from this topic, visit https://groups.google.com/d/topic/kobo-users/kh8QEkLzVGI/unsubscribe.

To unsubscribe from this group and all its topics, send an email to kobo-users+unsubscribe@googlegroups.com.

To post to this group, send email to kobo-...@googlegroups.com.

Visit this group at https://groups.google.com/group/kobo-users.

For more options, visit https://groups.google.com/d/optout.

Dear Jake

I have test your method completely in my office and it is accessible from Internet and also generate the certificates from Letsencrypt. Those who are struggling with kobo Toolbox deployment on private server, Please follow the Jake’s Method.

Regards,

Kaleem

···

On Friday, July 28, 2017 at 7:19:08 PM UTC+5, Kaleem Qureshi wrote:

Are you available now

On 24 Jun 2017 7:45 pm, “jpstaub” jpst...@gmail.com wrote:

Hello Kaleem,

No changes should be required in jwilder/nginx-proxy. See attached docker-compose file for what I use to start a jwilder/nginx-proxy container.

To eliminate potential port conflict problems stop all containers that are not part of the KoBoToolbox deployment.

Also, to ensure the Ubuntu server firewall is not creating problems disable the firewall during deployment troubleshooting efforts.

Regards,
Jake

On Tuesday, June 20, 2017 at 6:50:49 AM UTC-4, Kaleem Qureshi wrote:

Thanks Jake, When we run the jwilder/nginx and kobo toolbox, then error comes "driver failed programming external connectivity kobo docker nginx jwilder* . I think port conflict problem. please let me that is there any change needed in docker-compose.yml file in nginx/jwilder .

Regards,
kaleem

On Thursday, June 8, 2017 at 5:48:47 PM UTC+5, jpstaub wrote:

Good morning Kaleem,

One more thing, I have login from super user , working fine . but when I create the user with djang adminsitration. User can not create the form and deploy the project?

It sounds like you have not set User permissions correctly for the user in question. On Django site administration see:
Home >> Authentication and Authorization >> Users >> User of Interest >> Permissions (Check Active) >> User permissions (select required permission for User of Interest).

Regards,
Jake

You received this message because you are subscribed to a topic in the Google Groups “Kobo Users” group.

To unsubscribe from this topic, visit https://groups.google.com/d/topic/kobo-users/kh8QEkLzVGI/unsubscribe.

To unsubscribe from this group and all its topics, send an email to kobo-users+unsubscribe@googlegroups.com.

To post to this group, send email to kobo-...@googlegroups.com.

Visit this group at https://groups.google.com/group/kobo-users.

For more options, visit https://groups.google.com/d/optout.

Sorry When I create the form and deploy it , It generate Server Error 500. I have check on both version http and https.

It works perfactly when we test on local machine . Each and every thing working properly, I face the problem on deployment

···

On Wed, Aug 2, 2017 at 11:27 AM, Kaleem Qureshi kaleemq...@gmail.com wrote:

Dear Jake

I have test your method completely in my office and it is accessible from Internet and also generate the certificates from Letsencrypt. Those who are struggling with kobo Toolbox deployment on private server, Please follow the Jake’s Method.

Regards,

Kaleem

On Friday, July 28, 2017 at 7:19:08 PM UTC+5, Kaleem Qureshi wrote:

Are you available now

On 24 Jun 2017 7:45 pm, “jpstaub” jpst...@gmail.com wrote:

Hello Kaleem,

No changes should be required in jwilder/nginx-proxy. See attached docker-compose file for what I use to start a jwilder/nginx-proxy container.

To eliminate potential port conflict problems stop all containers that are not part of the KoBoToolbox deployment.

Also, to ensure the Ubuntu server firewall is not creating problems disable the firewall during deployment troubleshooting efforts.

Regards,
Jake

On Tuesday, June 20, 2017 at 6:50:49 AM UTC-4, Kaleem Qureshi wrote:

Thanks Jake, When we run the jwilder/nginx and kobo toolbox, then error comes "driver failed programming external connectivity kobo docker nginx jwilder* . I think port conflict problem. please let me that is there any change needed in docker-compose.yml file in nginx/jwilder .

Regards,
kaleem

On Thursday, June 8, 2017 at 5:48:47 PM UTC+5, jpstaub wrote:

Good morning Kaleem,

One more thing, I have login from super user , working fine . but when I create the user with djang adminsitration. User can not create the form and deploy the project?

It sounds like you have not set User permissions correctly for the user in question. On Django site administration see:
Home >> Authentication and Authorization >> Users >> User of Interest >> Permissions (Check Active) >> User permissions (select required permission for User of Interest).

Regards,
Jake

You received this message because you are subscribed to a topic in the Google Groups “Kobo Users” group.

To unsubscribe from this topic, visit https://groups.google.com/d/topic/kobo-users/kh8QEkLzVGI/unsubscribe.

To unsubscribe from this group and all its topics, send an email to kobo-users+unsubscribe@googlegroups.com.

To post to this group, send email to kobo-...@googlegroups.com.

Visit this group at https://groups.google.com/group/kobo-users.

For more options, visit https://groups.google.com/d/optout.

You received this message because you are subscribed to a topic in the Google Groups “Kobo Users” group.

To unsubscribe from this topic, visit https://groups.google.com/d/topic/kobo-users/kh8QEkLzVGI/unsubscribe.

To unsubscribe from this group and all its topics, send an email to kobo-users+unsubscribe@googlegroups.com.

To post to this group, send email to kobo-...@googlegroups.com.

Visit this group at https://groups.google.com/group/kobo-users.

For more options, visit https://groups.google.com/d/optout.

With Best Regards,
Kaleem Ahmad Qureshi

Regional ICT Infrastructure Engineer South Asia Region

***Country Office Pakistan, ***

Islamic Relief World Wide UK ,

Cell: 92 300 8521825 , 92 333 5135815.