loomio-deploy updated
Robert Guthrie PublicSeen by 75I've just pushed a reasonably big change up to the loomio/loomio-deploy repo.
The major change here is that we use nginx as a https frontend, and automatically manage issuing and renewing your SSL certificates.
I'm keen to hear how it goes for you.
Sorry but I don't know what a UTM proxy is. If you access the host directly does it work?
Hello
I'd tried this morning to connect to loomio with the URL https://IP_of_my_loomio_vm it's doesn't work
I have this message:
Connexion failed
firefox can't established connexion with server 172.16.0.85.
this is the result of docker ps:
docker ps
CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES
4fdebe49d4cb jrcs/letsencrypt-nginx-proxy-companion "/bin/bash /app/entry" 2 days ago Up 2 days loomiodeploy_letsencrypt_1
f48a2113cb1b jwilder/nginx-proxy "/app/docker-entrypoi" 2 days ago Up 2 days 0.0.0.0:80->80/tcp, 0.0.0.0:443->443/tcp loomiodeploy_nginx_1
7bea4d788027 loomio/mailin-docker "/bin/sh -c 'mailin -" 2 days ago Up 2 days 25/tcp, 0.0.0.0:32768->1525/tcp loomiodeploy_mailin_1
acbcaa912ba2 loomio/loomio "/bin/sh -c 'bundle e" 2 days ago Up 2 days 3000/tcp loomiodeploy_loomio_1
6d54ce57b7ab loomio/loomio "bundle exec rake job" 2 days ago Up 2 days 3000/tcp loomiodeploy_worker_1
8ebb1c6d55b0 loomiodeploy_faye "/bin/sh -c 'thin --p" 2 days ago Up 2 days 3000/tcp loomiodeploy_faye_1
fce6a5608c50 postgres "/docker-entrypoint.s" 2 days ago Up 2 days 5432/tcp loomiodeploy_db_1
Not having touched the server since last week so I have just tried to connect with the local url (https://172.16.0.85) and here is the return which I have:
503 Service Temporarily Unavailable
nginx/1.9.12
all docker service always run and i'm using Ubuntu server 14.04 LTS
Thank you for your help
If it's saying that, and you just started it... you might just need to wait another 30 seconds for it to finish booting. Otherwise, look at the logs docker-compose logs and see what the rails server is saying.
hi
i always have this message
503 Service Temporarily Unavailable
nginx/1.9.12
I do have an error related to let's encrypt (see file)
It's saying that let's encrypt is not able to verify you are the owner of the domain.
I've had that error before and in my case I fixed it by opening port 80, because letsencrypt needs port 80 and 443 to do it's job.
thank you
So i have just opened the port 80
How can i regen the letsencrypt validation?
It should automatically retry when you restart it. Check the logs again.
i restarted the server, and do a docker-compose up -d for start loomio server
docker ps
CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES
4fdebe49d4cb jrcs/letsencrypt-nginx-proxy-companion "/bin/bash /app/entry" 9 days ago Up 22 minutes loomiodeploy_letsencrypt_1
f48a2113cb1b jwilder/nginx-proxy "/app/docker-entrypoi" 9 days ago Up 22 minutes 0.0.0.0:80->80/tcp, 0.0.0.0:443->443/tcp loomiodeploy_nginx_1
7bea4d788027 loomio/mailin-docker "/bin/sh -c 'mailin -" 9 days ago Up 22 minutes 25/tcp, 0.0.0.0:32768->1525/tcp loomiodeploy_mailin_1
acbcaa912ba2 loomio/loomio "/bin/sh -c 'bundle e" 9 days ago Up 22 minutes 3000/tcp loomiodeploy_loomio_1
6d54ce57b7ab loomio/loomio "bundle exec rake job" 9 days ago Up 22 minutes 3000/tcp loomiodeploy_worker_1
8ebb1c6d55b0 loomiodeploy_faye "/bin/sh -c 'thin --p" 9 days ago Up 22 minutes 3000/tcp loomiodeploy_faye_1
fce6a5608c50 postgres "/docker-entrypoint.s" 10 days ago Up 22 minutes 5432/tcp loomiodeploy_db_1
the logs are the same, there are no news logs
after a docker-compose restart:
docker-compose restart
Restarting loomiodeploy_letsencrypt_1 ... done
Restarting loomiodeploy_nginx_1 ...
Restarting loomiodeploy_mailin_1 ... done
Restarting loomiodeploy_loomio_1 ... done
Restarting loomiodeploy_worker_1 ... done
Restarting loomiodeploy_faye_1 ... done
Restarting loomiodeploy_db_1 ... done
ERROR: for loomiodeploy_nginx_1 UnixHTTPConnectionPool(host='localhost', port=None): Read timed out. (read timeout=60)
ERROR: An HTTP request took too long to complete. Retry with --verbose to obtain debug information.
If you encounter this issue regularly because of slow network conditions, consider setting COMPOSE_HTTP_TIMEOUT to a higher value (current value: 60).
try docker-compose down then docker-compose up -d
docker-compose down
Stopping loomiodeploy_letsencrypt_1 ... done
Stopping loomiodeploy_nginx_1 ...
Stopping loomiodeploy_mailin_1 ... done
Stopping loomiodeploy_loomio_1 ... done
Stopping loomiodeploy_worker_1 ... done
Stopping loomiodeploy_faye_1 ... done
Stopping loomiodeploy_db_1 ... done
ERROR: for loomiodeploy_nginx_1 UnixHTTPConnectionPool(host='localhost', port=None): Read timed out. (read timeout=70)
ERROR: An HTTP request took too long to complete. Retry with --verbose to obtain debug information.
If you encounter this issue regularly because of slow network conditions, consider setting COMPOSE_HTTP_TIMEOUT to a higher value (current value: 60).
so can't stop loomiodeploy_nginx_1
docker ps
CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES
f48a2113cb1b jwilder/nginx-proxy "/app/docker-entrypoi" 10 days ago Up 50 minutes 0.0.0.0:80->80/tcp, 0.0.0.0:443->443/tcp loomiodeploy_nginx_1
so i restarted the server
just after restart i have:
docker ps
CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES
and i do: docker-compose up -d
after this i have
docker-compose up -d
Starting loomiodeploy_faye_1
Starting loomiodeploy_db_1
Starting loomiodeploy_worker_1
Starting loomiodeploy_loomio_1
Starting loomiodeploy_mailin_1
Starting loomiodeploy_nginx_1
Starting loomiodeploy_letsencrypt_1
everything seems to be ok
and the log are on the file joined
it's not works
You need a successful docker-compose down to remove the containers. Looks like you're restarting existing containers rather than creating new ones.
Are you sure that port 80 is mapped correctly? Looks like the same problem as before.
Don't know why but today "docker-compose down" works and all containers are stopped and removed even nginx.
"docker-compose up -d" ok
You're right i have a problem with the mapping of port 80 and 443 cause i try to redirect theses ports through a VPN.
I correct the problem and inform you
Hi
I'm also getting errors with https and http access.
I just created an issue on loomio-deploy's GitHub project (https://github.com/loomio/loomio-deploy/issues/3).
It could be discussed in this thread or on the issue, as you want.
rgds,
Louis
Hi you need an internet connection for Lets encrypt to work properly in creating the certs.
(This is due to the cross signing needing to be done online from your end to their intermediary, this also applies to other cert authorities.)
In order to at least temporarily resolve the issue, you need to be online, have the domain on that machine and register that domain as part of the Lets encrypt process (which as I recall uses nginx.) You should then be able at least to import the key pair into your server and get loomio working.
Hi Andrew. Thank you for your reply.
It would not be so easy to make our server accessible from internet.
Would it be possible to use http only?
Although you only need to be online while you obtain certificates, it may be possible if you have it configured to only use http to have it entirely offline.
I am looking to install an instance of loomio on an obsolete laptop shortly, however that would be online basically all the time.
(problems with half-wit chorus nz fibre installers in the neighbourhood should not occur again.)
Hi everybody
sorry for my long silence due to holidays and other priorities in my job.
So i have installed an apache reverse proxy server in my local network (hard to configure to works with nginx loomio server) and now i can access to my local loomio server with the address https://loomio.mydomain.com, it's great.
but i have a problem again
When I want to log me, the server does not recognize my email adress and password. So i clic on "forgot password" icon, enter my email adress and the system tell me that my email adress is invalid.
How can i solved this problem?
There is a login and a password by default for an admin or for the manual creation of the users?
Thank you for your help.
Hi, Welcome back.
You can visit the /users/sign_up path to start an account.
thank you very much it's working 👍
it's possible to insert a "create account" link or icon on the login page? how can i do it?
Many thanks
after severals tests I have the following comments:
- Loomio-deploy works 👍
- I'd installed it on virtualmachine with 1go ram (ubuntu server 14.04LTS) so loomio is very slow, so, how much of ram do you recommend for the server?
On the other hand, I have another problem, we do not receive the e-mails of loomio
my smtp setting on env file:
smtp settings
SUPPORT_EMAIL=informatique@mydomain.com
SMTP_DOMAIN=loomio.mydomain.com
SMTP_SERVER=smtp.fai.net
SMTP_PORT=465
SMTP_USERNAME=support@mydomain.com
SMTP_PASSWORD= mypassword
FAYE_URL=https://faye.loomio.mydomain.com/faye
REPLY_HOSTNAME=loomio.mydomain.com
Extract of the file of log:
worker_1 |
worker_1 | Sent mail to test@mydomain.com (60072.0ms)
worker_1 | [Worker(host:21c6de5ca23f pid:1)] Job ThreadMailer.send (id=705) FAILED (0 prior attempts) with Net::ReadTimeout: Net::ReadTimeout
worker_1 | 2016-05-25T09:06:35+0000: [Worker(host:21c6de5ca23f pid:1)] Job ThreadMailer.send (id=705) FAILED (0 prior attempts) with Net::ReadTimeout: Net::ReadTimeout
worker_1 | [Worker(host:21c6de5ca23f pid:1)] Job ThreadMailer.send (id=706) RUNNING
worker_1 | 2016-05-25T09:06:35+0000: [Worker(host:21c6de5ca23f pid:1)] Job ThreadMailer.send (id=706) RUNNING
Thank you for your help
There are also other threads in this group where ubuntu 14.04 seems to have issues. See
https://www.loomio.org/d/MFvCj6fc/i-can-t-get-development-environment-running-on-ubuntu-14-04
https://www.loomio.org/d/F0Hw9zAC/how-to-install-loomio-in-ubuntu-14-04-
https://www.loomio.org/d/ar62Nty4/automated-setup-of-development-environment-ubuntu-14-04-lts (This is the thread where you got your loomio working, am including this link for my reference on how to get things setup.)
SMTP_SERVER should be smtp.mydomain.com
if smtp server does not match smtp domain (loomio.mydomain.com), then it will not be sending through the emails from loomio.
Thank you
I'd installed exim4 on my server for smtp smarthost
In env file which is the variable of smtp TLS?
SMTP TLS/SSL required: yes
or
SMTP_TLS_required=yes
or others format?
Thank you
I think the TLS/SSL setting is automatic.. meaning it will try to use it and fall back if it is not available.
pfff loomio always don't send email so it's not completely working
I'd installed exim4 on my server, and my server can send emails (tested)
I connect on loomio and loomio not sending e-mails.
i try to modified env file like describe here https://www.digitalocean.com/community/tutorials/how-to-use-google-s-smtp-server, no result
i always have this error message:
worker_1 | Sent mail to xxx@gmail.com (60043.0ms)
worker_1 | [Worker(host:d49fd2a2ca42 pid:1)] Job InvitePeopleMailer.to_join_group (id=885) FAILED (0 prior attempts) with Net::ReadTimeout: Net::ReadTimeout
worker_1 | 2016-05-27T08:27:41+0000: [Worker(host:d49fd2a2ca42 pid:1)] Job InvitePeopleMailer.to_join_group (id=885) FAILED (0 prior attempts) with Net::ReadTimeout: Net::ReadTimeout
when i'm restarting docker i see theses logs
mailin_1 | info: Mailin v3.0.3
mailin_1 | info: Webhook url: http://loomio:3000/email_processor/
mailin_1 | info: Log file: /var/log/mailin.log
mailin_1 | info: Mailin Smtp server listening on port 25
mailin_1 | warn: Webhook http://loomio:3000/email_processor/ seems invalid or down. You may want to double check the webhook url.
this is my env file:
this is the hostname of your app used by loomio
CANONICAL_HOST=loomio.domain.com
this is to tell nginx that you want requests for this hostname to come to the app
VIRTUAL_HOST=loomio.domain.com
this is to configure letsencrypt to automatically issue and renew your hostname
LETSENCRYPT_HOST=loomio.domain.com
LETSENCRYPT_EMAIL=informatique@domain.com
the number of dots in your hostname
TLD_LENGTH=2
smtp settings
SUPPORT_EMAIL=informatique@domain.com
SMTP_DOMAIN=emailprovider.net
SMTP_SERVER=smtp.emailprovider.net
SMTP_PORT=465
SMTP_USERNAME=support@domain.com
SMTP_PASSWORD=mypassword
FAYE_URL=https://faye.loomio.domain.com/faye
REPLY_HOSTNAME=loomio.domain.com
helper bot is the account which welcomes people to their groups.
HELPER_BOT_EMAIL=informatique@domain.com
RAILS_ENV=production
FORCE_SSL=1
DEVISE_SECRET=8BE......................Lka4hD
SECRET_COOKIE_TOKEN=7hhnak...............QZuEoJ
PRIVATE_PUB_SECRET_TOKEN=JxUU2L8.............HcKG1uC4LWk
I don't understand what's happening and why it's don't works
It looks like support_email is not the same domain as smtp_domain
so perhaps the email not coming from the same domain name is your problem ?
may be but in my situation
i have an external provider for all my email management, I don't have a local server for emails management.
with exim4 i'm using my external provider smtp server for sending email (and it's works), i only want to do the same thing for sending email with loomio
so the address informatique@emailprovider.net don't exist, only the address informatique@domain.com exist
hi
I solved my problem by installing postfix in smtp relay on my server
In this case smtp in env file must be like this:
SUPPORT_EMAIL=support@mydomain.com
SMTP_DOMAIN=mydomain.lan
SMTP_SERVER=ip_of_smtp_server
SMTP_PORT=25
FAYE_URL=https://faye.loomio.mydomain.com/faye
REPLY_HOSTNAME=loomio.mydomain.com
Hi FSF,
I am trying to do the same. How did you set your postix server? Did you have to add username and password in etc/postfix/sasl_passwd?
Loomio SMTP settings are very frustrating.
Other thing,
When i create a group, answer to a proposal, or create a new proposal, the page don't auto refresh.
I must manually refresh the page with F5
there is a modification to make somewhere in a file for auto refresh the pages after a validation?
i see theses errors messages on logs:
nginx_1 | nginx.1 | 2016/05/31 09:35:47 [error] 30#30: *486 connect() failed (111: Connection refused)while connecting to upstream, client: 172.16.0.15, server: loomio.mydomain.com, request: "POST /ahoy/events HTTP/1.1", upstream: "http://172.17.0.4:3000/ahoy/events", host: "loomio.mydomain.com", referrer: "https://loomio.mydomain.com/d/xPfHy1Rh/mypost_test"
nginx_1 | nginx.1 | 2016/05/31 09:35:47 [warn] 30#30: *486 upstream server temporarily disabled while connecting to upstream, client: 172.16.0.15, server: loomio.mydomain.com, request: "POST /ahoy/events HTTP/1.1", upstream: "http://172.17.0.4:3000/ahoy/events", host: "loomio.mydomain.com", referrer: "https://loomio.mydomain.com/d/xPfHy1Rh/mypost_test"
This appears to be a IP address fault based on not having (Http error 486) resolved.
I'd refer you to https://en.wikipedia.org/wiki/List_of_HTTP_status_codes
However it seems it's error 496 in nginx, so SSL certificate required would be the one.
Does that sound like your server, no SSL certificate ? If so, you can rerun letsencrypt while online to get a current certificate, then you should have it going.
(of course if you did run letsencrypt 3 months ago last time, it will expire . older letsencrypt certificate don't support windows XP browsers, but the current version of letsencrypt certificate do.)
thank you
I solved this problem of error 486 by adding rules for faye.loomio.mydomain.com rules (http and https) in my apache reverse proxy
But it's really crazy; now i have an other error
nginx_1 | nginx.1 | 2016/06/01 07:19:04 [error] 41#41: *13 connect() failed (111: Connection refused) while connecting to upstream, client:172.16.0.15, server: loomio.mydomain.com, request: "GET /client/0.20.4/app.min.css HTTP/1.1", upstream: "http://172.17.0.4:3000/client/0.20.4/app.min.css", host: "loomio.mydomain.com", referrer: "https://loomio.mydomain.com/d/xPfHy1Rh/mypost_test-"
Hi, it appears this is the case which I had thought about yesterday night but considered less likely. However you are still getting problems, so I think the following is your problem :
You are getting connection refused due to a non-existant URI , so it would seem you are linking to something which isn't there.
Is it possible that client and server are not on the same subnet that you are getting the problem ? 172.16.0.15 client and 172.17.0.4 server ?
Thank you for your answer
172.16.0.15 is my reverse proxy server
172.16.0.85 is my vm who host loomio
172.17.0.xxx is loomio-docker in the host 172.16.0.85
172.16.0.15 can contact and speak with 172.16.0.85 (loomio works on port 80 and 443)
the network config on the host:
docker0 Link encap:Ethernet HWaddr 02:42:08:6d:dc:00
inet adr:172.17.0.1 Bcast:0.0.0.0 Masque:255.255.0.0
adr inet6: fe80::42:8ff:fe6d:dc00/64 Scope:Lien
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
Packets reçus:27983 erreurs:0 :0 overruns:0 frame:0
TX packets:32649 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 lg file transmission:0
Octets reçus:34422152 (34.4 MB) Octets transmis:14697907 (14.6 MB)
eth0 Link encap:Ethernet HWaddr 00:15:5d:00:02:27
inet adr:172.16.0.85 Bcast:172.16.0.255 Masque:255.255.255.0
adr inet6: fe80::215:5dff:fe00:227/64 Scope:Lien
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
Packets reçus:281033 erreurs:0 :0 overruns:0 frame:0
TX packets:41802 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 lg file transmission:1000
Octets reçus:53750761 (53.7 MB) Octets transmis:43144793 (43.1 MB)
lo Link encap:Boucle locale
inet adr:127.0.0.1 Masque:255.0.0.0
adr inet6: ::1/128 Scope:Hôte
UP LOOPBACK RUNNING MTU:65536 Metric:1
Packets reçus:0 erreurs:0 :0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 lg file transmission:0
Octets reçus:0 (0.0 B) Octets transmis:0 (0.0 B)
veth0256652 Link encap:Ethernet HWaddr 62:f0:9b:58:f6:82
adr inet6: fe80::60f0:9bff:fe58:f682/64 Scope:Lien
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
Packets reçus:11 erreurs:0 :0 overruns:0 frame:0
TX packets:94 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 lg file transmission:0
Octets reçus:806 (806.0 B) Octets transmis:6808 (6.8 KB)
veth275b50c Link encap:Ethernet HWaddr ce:a2:fd:c5:22:d8
adr inet6: fe80::cca2:fdff:fec5:22d8/64 Scope:Lien
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
Packets reçus:42715 erreurs:0 :0 overruns:0 frame:0
TX packets:39880 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 lg file transmission:0
Octets reçus:26363606 (26.3 MB) Octets transmis:22338487 (22.3 MB)
veth616846c Link encap:Ethernet HWaddr ca:a5:e9:d1:6f:12
adr inet6: fe80::c8a5:e9ff:fed1:6f12/64 Scope:Lien
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
Packets reçus:41002 erreurs:0 :0 overruns:0 frame:0
TX packets:22936 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 lg file transmission:0
Octets reçus:11893852 (11.8 MB) Octets transmis:12705718 (12.7 MB)
veth6a027a8 Link encap:Ethernet HWaddr a2:66:b3:e8:a7:39
adr inet6: fe80::a066:b3ff:fee8:a739/64 Scope:Lien
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
Packets reçus:39717 erreurs:0 :0 overruns:0 frame:0
TX packets:65467 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 lg file transmission:0
Octets reçus:27534142 (27.5 MB) Octets transmis:15804611 (15.8 MB)
veth7e4b7d2 Link encap:Ethernet HWaddr fe:ae:f5:c3:b0:e3
adr inet6: fe80::fcae:f5ff:fec3:b0e3/64 Scope:Lien
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
Packets reçus:8 erreurs:0 :0 overruns:0 frame:0
TX packets:83 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 lg file transmission:0
Octets reçus:648 (648.0 B) Octets transmis:5966 (5.9 KB)
vetha59ebbf Link encap:Ethernet HWaddr 2a:ef:c8:0e:90:e7
adr inet6: fe80::28ef:c8ff:fe0e:90e7/64 Scope:Lien
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
Packets reçus:46 erreurs:0 :0 overruns:0 frame:0
TX packets:137 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 lg file transmission:0
Octets reçus:4085 (4.0 KB) Octets transmis:12561 (12.5 KB)
vethfe379a4 Link encap:Ethernet HWaddr ea:b5:20:f1:29:30
adr inet6: fe80::e8b5:20ff:fef1:2930/64 Scope:Lien
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
Packets reçus:37055 erreurs:0 :0 overruns:0 frame:0
TX packets:35968 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 lg file transmission:0
Octets reçus:31354010 (31.3 MB) Octets transmis:29548419 (29.5 MB)
this is the iptable of my host VM (iptables modified my loomio docker install)
Chain INPUT (policy ACCEPT)
target prot opt source destination
Chain FORWARD (policy ACCEPT)
target prot opt source destination
DOCKER-ISOLATION all -- anywhere anywhere
DOCKER all -- anywhere anywhere
ACCEPT all -- anywhere anywhere ctstate RELATED,ESTABLISHED
ACCEPT all -- anywhere anywhere
ACCEPT all -- anywhere anywhere
Chain OUTPUT (policy ACCEPT)
target prot opt source destination
Chain DOCKER (1 references)
target prot opt source destination
ACCEPT tcp -- anywhere 172.17.0.6 tcp dpt:prospero-np
ACCEPT tcp -- anywhere 172.17.0.7 tcp dpt:https
ACCEPT tcp -- anywhere 172.17.0.7 tcp dpt:http
Chain DOCKER-ISOLATION (1 references)
target prot opt source destination
RETURN all -- anywhere anywhere
and the result of docker ps
docker ps
CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES
78b613fbfd13 jrcs/letsencrypt-nginx-proxy-companion "/bin/bash /app/entry" 23 hours ago Up 23 hours loomiodeploy_letsencrypt_1
8fdffc733c98 jwilder/nginx-proxy "/app/docker-entrypoi" 23 hours ago Up 23 hours 0.0.0.0:80->80/tcp, 0.0.0.0:443->443/tcp loomiodeploy_nginx_1
4316c234e4a4 loomio/mailin-docker "/bin/sh -c 'mailin -" 23 hours ago Up 23 hours 25/tcp, 0.0.0.0:32771->1525/tcp loomiodeploy_mailin_1
2802fe7ed964 loomio/loomio "/bin/sh -c 'bundle e" 23 hours ago Up 23 hours 3000/tcp loomiodeploy_loomio_1
ea4d32fe9d68 loomio/loomio "bundle exec rake job" 23 hours ago Up 23 hours 3000/tcp loomiodeploy_worker_1
89092afa104f postgres "/docker-entrypoint.s" 23 hours ago Up 23 hours 5432/tcp loomiodeploy_db_1
8d5c3c389839 loomiodeploy_faye "/bin/sh -c 'thin --p" 23 hours ago Up 23 hours 3000/tcp loomiodeploy_faye_1
so may be i must had a rule in docker to make accessible the port 3000 of the docker on the local area network in chain docker of iptables like this:
ACCEPT tcp -- anywhere 172.17.0.4 tcp:3000
or modified 8fdffc733c98 jwilder/nginx-proxy "/app/docker-entrypoi" 23 hours ago Up 23 hours 0.0.0.0:80->80/tcp, 0.0.0.0:443->443/tcp
to add rules for port 3000
But i don't know how doing this
Numerous companies and private individuals use reverse proxy server and solve this problem would be a good thing
It's not really block Loomio, it's only block the automatic refresh of the page in Loomio.
It has only just now updated the refresh from your reply by email, so it maybe a wider problem.
I would suggest that this should be possible in docker, however I have yet to begin with that.
Effectively, it's may be a problem that can be solved in docker
May be @robertguthrie can help me
Hi @fsf1967 I'd suggest that you check the forums of docker : https://forums.docker.com/ hopefully you can find the solution there.
Sorry, I don't understand the problem.
thank you
i try to find a solution to this forum, and if i find i'll post the answer here
hi
may be i find a solution to my problem
i must add some line in nginx configuration for adding backend access to nginx proxy like they write in this forum
How can i do this?
Thank you
You're asking an nginx question, not a loomio question. I don't don't know how to do what you want to do. I'm really sorry.
problem solved 👍
as my loomio is installed behind a local apache proxy, i'd used an auto signed https certificate in my /etc/apache2/sites-avalaible/loomio.conf file of my apache reverse proxy.
Til today i'm using letsencrypt certificate and everything works perfectly.
I don't now how a certificate can create such communications problem between 2 servers.
great to hear to resolved the issue.
Me too 😅
I moreover posted the answer here so that it is of use to others if they want to install loomio behind an apache or nginx reverse proxy.
sorry but today i'd stop the server to make a backup,
i restart it, and i have the message:
Service Unavailable
The server is temporarily unable to service your request due to maintenance downtime or capacity problems. Please try again later.
docker ps is ok
CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES
0a51804476c3 jrcs/letsencrypt-nginx-proxy-companion "/bin/bash /app/entry" 4 days ago Up 7 minutes loomiodeploy_letsencrypt_1
50c2ae81b8f2 loomio/mailin-docker "/bin/sh -c 'mailin -" 4 days ago Up 7 minutes 25/tcp, 0.0.0.0:32769->1525/tcp loomiodeploy_mailin_1
0442631f6d5f loomio/loomio "/bin/sh -c 'bundle e" 4 days ago Up 7 minutes 3000/tcp loomiodeploy_loomio_1
72fc0993ce07 loomio/loomio "bundle exec rake job" 4 days ago Up 7 minutes 3000/tcp loomiodeploy_worker_1
45dff9dc0dc8 loomiodeploy_faye "/bin/sh -c 'thin --p" 4 days ago Up 7 minutes 3000/tcp loomiodeploy_faye_1
8cc5124068cb postgres "/docker-entrypoint.s" 4 days ago Up 7 minutes 5432/tcp loomiodeploy_db_1
what's happening again?
edit: after 2 restarts loomio works again !!
sounds like you need to look at the logs for the application server.
docker logs loomiodeploy_loomio_1
I installed the new loomio-deploy yesterday on my server by using the dns from ovh for the rerouting to my public ip, and my UTM https proxy does a snat to the ip of my loomio VM.
The UTM https proxy works perfectly with all my apache servers.
I had no error message during the installation
When i open the url https://loomio.mydomain.com i have this message:
Failure of the secure connection
The connection with loomio.mydomain.com was interrupted during the load of the page.
Thank you for your help