deeztek/deeztek-docker

building and starting of Nextcloud-Signal Docker Cotainers Fails

Still-not-found opened this issue · 16 comments

Still-not-found commented

after it auto generates the shared key and secret key , it throws an error
Building Nextcloud-Signal Docker Containers... [FAIL]
Starting Nextcloud-Signal Docker Containers... [FAIL]

How to resolve this issue? please share any ideas to resolve this issue

deeztek commented

There should be an install_log-[timestamp].log file in the same directory you started the install script. Take a look in that file for the cause of the error. You can always post here ensuring that you remove any sensitive info.

thanks

Still-not-found commented
Still-not-found commented

Sir,actually the "ubuntu_install_nextcloud_signal.sh" script fails to build and deploy these containers that are mentioned below ,would you please suggest a solution for this?

  • nextcloud_spreed_nginx
  • nextcloud_spreed_backend
  • nextcloud_spreed_janus
  • nextcloud_spreed_coturn
  • nextcloud_spreed_nats
  • nextcloud_spreed_certbot.
deeztek commented

I'm going to need more information than simply "script fails to build and deploy". What does the install log say? Do you have docker-compose installed?

Still-not-found commented
deeztek commented

The only limiting factor should be your signaling server resources.

Still-not-found commented
deeztek commented

As previously mentioned:

There should be an install_log-[timestamp].log file in the same directory you started the install script. Take a look in that file for the cause of the error. You can always post here ensuring that you remove any sensitive info.

Unless you provide the install log, I cannot help you.

Still-not-found commented
StephanEto commented

Hi,
i have the same issue at the same position run with Ubuntu 20.04. All Prequisites are okay.
Following entry in the install_log file:
Building Nextcloud-Signal Docker Containers build path /opt/nextcloud-spreed-signaling/docker/coturn either does not exist, is not accessible, or is not a valid URL.
Thank you!

deeztek commented

There should be an install_log-[timestamp].log file in the same directory you started the install script. Please provide script so that I can take a look.

deeztek commented

Thank you. Let me take a look. There also seems to be a change with the nextcloud-spreed repo and the way it the docker installation works now. Let me work on it and get back to you asap.

deeztek commented

Commit b017a6e should fix all the issues you are experiencing.

How to re-deploy:

  • bring down any containers that were created/started from the /opt/nextcloud-spreed-signaling directory: docker-compose down
  • remove any volumes if they exist (most likely will be removed after the docker-compose down command)
  • remove the spreed network that was previously created: docker network rm spreed
  • remove the /opt/nextcloud-spreed-signaling directory: rm -rf /opt/nextcloud-spreed-signaling
  • remove the deeztek-docker repository
  • git clone the deeztek-docker repository
  • run the install script: sudo bash ubuntu_install_nextcloud_signal.sh

This was tested on Ubuntu 18.04 LTS but they shouldn't be a problem with newer version. Please let me know if any. Bonus: this now works with newest version of Nextcloud.

StephanEto commented

Hey deeztek,

thank you for update the script! Please check out line 462 in ubuntu_install_nextcloud_signal.sh:
I had to change /usr/local/bin/docker to /usr/bin/docker . Then it worked perfectly.
Best regards!

deeztek commented

Thanks for the feedback! Fixed with 136a43b.