sandstorm

sandstorm copied to clipboard

-installing the script i get a failure at register at lets encrypt: it wanted to install it to port 6080, but the config is at port 80 and it cant start:

** Starting Sandstorm at: Mon Jul 19 23:20:54 2021 *** Uncaught exception *** sandstorm/run-bundle.c++:1878: failed: bind(sockFd, reinterpret_cast<sockaddr *>(&sa), sizeof(sockaddr_in)): Address already in use stack: 613814 612195 610f5b 61060c 505dcb 5059bb

SERVER_USER=sandstorm PORT=80 MONGO_PORT=6081 BIND_IP=0.0.0.0 BASE_URL=https://xxx.sandcats.io WILDCARD_HOST=*.xxx.sandcats.io UPDATE_CHANNEL=dev ALLOW_DEV_ACCOUNTS=false SMTP_LISTEN_PORT=30025 SANDCATS_BASE_DOMAIN=sandcats.io HTTPS_PORT=443

NOTE: It looks like your system already has some other web server installed (port 80 and/or 443 are taken), so Sandstorm cannot act as your main web server.

  This script can set up Sandstorm to run on port 6080 instead,
  without HTTPS. This makes sense if you're OK with typing the port number
  into your browser whenever you access Sandstorm and you don't need
  security. This also makes sense if you are going to set up a reverse proxy;
  if so, see https://docs.sandstorm.io/en/latest/administering/reverse-proxy/

  If you want, you can quit this script with Ctrl-C now, and go uninstall
  your other web server, and then run this script again. It is also OK to
  proceed if you want.

Do you in fact have another web server running on the same box, as the error message suggests?

At first I wondered if this was going to be about https://letsencrypt.status.io/pages/incident/55957a99e800baa4470002da/60f5b56d1c82f805369a7d98

The install script should let you select port 6080 if you want to use it, but it might not be the shortest path through the installation to get there.

yes, iu have a normal apache running. The script select port 6080 as output text on terminal but it doesnt install it because of the "double webserver" issue. I installed it manually and it works, but it was only a hint that the installation script needs to get an upgrade

I'm still not totally clear on what the issue is; did the script not proceed with the :6080 installation after that prompt? What were you expecting to happen, and what happened instead?