So, I am certain I have a virgin database and whatnot. egroupware-rocketchat]# docker logs -f rocketchat Local egroupware-rocketchat]# docker-compose up -dĬreating network "egroupware-rocketchat_default" with the default driverĬreating volume "egroupware-rocketchat_mongo" with default driverĬreating egroupware-rocketchat_mongo-init-replica_1. Removing volume egroupware-rocketchat]# docker volume rm egroupware-rocketchat_mongoĮrror: No such volume: egroupware-rocketchat]# docker volume ls | grep egroupware-rocketchat]# docker volume ls Removing network egroupware-rocketchat_default Removing egroupware-rocketchat_mongo-init-replica_1. Local egroupware-rocketchat]# docker volume rm egroupware-rocketchat_mongoĮrror response from daemon: remove egroupware-rocketchat_mongo: volume is in use - egroupware-rocketchat]# docker-compose down -volumes egroupware-rocketchat]# docker volume ls | grep mongo I did have to use an additional command to the ones listed in the post you linked in your reply… egroupware-rocketchat]# docker-compose stop I did both things you suggested, but the blinking continued. PS: I tried to upload a short mp4 of the “blinking screen” but I’m too new a user to be allowed. Perhaps I am again missing something basic in configuration, but how do I resolve the “blinking configuration screen” issue? I tried to fill in the fields despite the blinking, but I could not even select a field to complete, let alone type anything into them. ➔ +-+Īnd the server now runs! BUT when I go to, the configuration screen comes up- yet it is rapidly “blinking” in and out between a readable screen and a grey one. Loaded the Apps Framework and loaded a total of 0 Apps!īrowserslist: caniuse-lite is outdated. Ufs: temp directory created at "/tmp/ufs" Then, I re-ran the log command: egroupware-rocketchat]# docker logs -f rocketchat Starting egroupware-rocketchat_mongo-init-replica_1. Then, I regenerated the rocketchat docker as you suggested: egroupware-rocketchat]# docker rm -f egroupware-rocketchat]# docker-compose up -d Per your suggestion, I have changed the link in my docker-compose.yml for rocketchat to be: I get this over and over in the log: /app/bundle/programs/server/node_modules/fibers/fibers.js:90Įrror: $ROOT_URL, if specified, must be an URL Sorry I was not more clear before, when I run: I am running a brand new v19 installation on a CentOS 8 host. Oh, yes… here’s my “docker ps -a”: ~]# docker ps -aĬONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMESĢ70796e734e2 mongo:4.0 "docker-entrypoint.s…" About an hour ago Exited (0) About an hour ago egroupware-rocketchat_mongo-init-replica_1ĭb6332c2b28a rocketchat/rocket.chat:latest "bash -c 'for i in `…" About an hour ago Up 2 minutes 127.0.0.1:3000->3000/tcp rocketchatĮcc2122a7bf8 mongo:4.0 "docker-entrypoint.s…" About an hour ago Up 26 minutes 27017/tcp rocketchat-mongoģcc7b556889e nginx:stable-alpine "nginx -g 'daemon of…" 2 hours ago Up 26 minutes 127.0.0.1:8080->80/tcp egroupware-nginxīd850e6ba921 containrrr/watchtower "/watchtower -sched…" 2 hours ago Up 26 minutes egroupware-watchtowerĮ0ad8e7f214d egroupware/egroupware:latest "/entrypoint.sh php-…" 2 hours ago Up 26 minutes 9000/tcp egroupwareħaad267bc392 quay.io/egroupware/collabora-key:stable "/bin/sh -c 'bash st…" 2 hours ago Up 26 minutes 127.0.0.1:9980->9980/tcp collabora-key etc/egroupware-rocketchat/docker-compose.yml: - ROOT_URL=Īm I missing something obvious? I have combed the documentation, this forum and the general Internet… etc/egroupware-rocketchat/docker-compose.yml: # IMPORTANT: change ROOT_URL to your actual url eg. Yet, if I look at the compose file, I have set the URL: ~]# grep -ir "ROOT_URL" /etc/* On the docker log side, I get this: Error: $ROOT_URL, if specified, must be an URLĪt /app/bundle/programs/server/boot.js:398:38Īt /app/bundle/programs/server/boot.js:226:21Īt /app/bundle/programs/server/boot.js:461:7Īt n (/app/bundle/programs/server/profile.js:280:14)Īt /app/bundle/programs/server/boot.js:460:13 The proxy server could not handle the request GET /rocketchat/. The proxy server received an invalid response from an upstream server. If I use the direct-URL method, I get the error: Proxy Error When trying to configure rocketchat, eGroupWare tells me it cannot connect.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |