AngryCvilleian

Members
  • Posts

    2
  • Joined

  • Last visited

AngryCvilleian's Achievements

Newbie

Newbie (1/14)

0

Reputation

  1. Having a real weird issue. After replacing some hardware (and a comedy of error) I had to reinstall NPM from scratch. Removed the docker, cleaned up remaining data, Reinstalled, ports 80/443 are being forwarded to 8080/4443, and I can log in. But the dashboard and proxy pages are blank. I can click on other dropdowns and they open but none of the links inside them are working. Nothing stands out in the logs (below) but I'm a noob. Anyone got any ideas? [s6-init] making user provided files available at /var/run/s6/etc...exited 0. [s6-init] ensuring user provided files have correct perms...exited 0. [fix-attrs.d] applying ownership & permissions fixes... [fix-attrs.d] done. [cont-init.d] executing container initialization scripts... [cont-init.d] 00-app-niceness.sh: executing... [cont-init.d] 00-app-niceness.sh: exited 0. [cont-init.d] 00-app-script.sh: executing... [cont-init.d] 00-app-script.sh: exited 0. [cont-init.d] 00-app-user-map.sh: executing... [cont-init.d] 00-app-user-map.sh: exited 0. [cont-init.d] 00-clean-logmonitor-states.sh: executing... [cont-init.d] 00-clean-logmonitor-states.sh: exited 0. [cont-init.d] 00-clean-tmp-dir.sh: executing... [cont-init.d] 00-clean-tmp-dir.sh: exited 0. [cont-init.d] 00-set-app-deps.sh: executing... [cont-init.d] 00-set-app-deps.sh: exited 0. [cont-init.d] 00-set-home.sh: executing... [cont-init.d] 00-set-home.sh: exited 0. [cont-init.d] 00-take-config-ownership.sh: executing... [cont-init.d] 00-take-config-ownership.sh: exited 0. [cont-init.d] 00-xdg-runtime-dir.sh: executing... [cont-init.d] 00-xdg-runtime-dir.sh: exited 0. [cont-init.d] 90-db-upgrade.sh: executing... [cont-init.d] 90-db-upgrade.sh: exited 0. [cont-init.d] nginx-proxy-manager.sh: executing... [1;34m❯ [1;36mEnabling IPV6 in hosts: [1;33m/etc/nginx/conf.d[0m [1;34m❯ [1;33m/etc/nginx/conf.d/default.conf[0m [1;34m❯ [1;33m/etc/nginx/conf.d/include/assets.conf[0m [1;34m❯ [1;33m/etc/nginx/conf.d/include/block-exploits.conf[0m [1;34m❯ [1;33m/etc/nginx/conf.d/include/force-ssl.conf[0m [1;34m❯ [1;33m/etc/nginx/conf.d/include/letsencrypt-acme-challenge.conf[0m [1;34m❯ [1;33m/etc/nginx/conf.d/include/proxy.conf[0m [1;34m❯ [1;33m/etc/nginx/conf.d/include/ssl-ciphers.conf[0m [1;34m❯ [1;33m/etc/nginx/conf.d/production.conf[0m [1;34m❯ [1;36mEnabling IPV6 in hosts: [1;33m/config/nginx[0m [1;34m❯ [1;33m/config/nginx/ip_ranges.conf[0m [1;34m❯ [1;33m/config/nginx/resolvers.conf[0m [cont-init.d] nginx-proxy-manager.sh: exited 0. [cont-init.d] done. [services.d] starting services [services.d] starting s6-fdholderd... [services.d] starting logmonitor... [services.d] starting statusmonitor... [logmonitor] no file to monitor: disabling service... [statusmonitor] no file to monitor: disabling service... [services.d] starting cert_cleanup... [services.d] starting logrotate... [services.d] starting nginx... [cert_cleanup] starting... [services.d] starting app... [logrotate] starting... [nginx] starting... [app] starting Nginx Proxy Manager... [services.d] done. [cert_cleanup] ---------------------------------------------------------- [cert_cleanup] Let's Encrypt certificates cleanup - 2021/01/28 22:52:08 [cert_cleanup] ---------------------------------------------------------- [cert_cleanup] 0 file(s) kept. [cert_cleanup] 0 file(s) deleted. [1/28/2021] [10:52:09 PM] [Migrate ] › ℹ info Current database version: none [1/28/2021] [10:52:09 PM] [IP Ranges] › ℹ info Fetching IP Ranges from online services... [1/28/2021] [10:52:09 PM] [IP Ranges] › ℹ info Fetching https://ip-ranges.amazonaws.com/ip-ranges.json [1/28/2021] [10:52:10 PM] [IP Ranges] › ℹ info Fetching https://www.cloudflare.com/ips-v4 [1/28/2021] [10:52:10 PM] [IP Ranges] › ℹ info Fetching https://www.cloudflare.com/ips-v6 [1/28/2021] [10:52:10 PM] [SSL ] › ℹ info Let's Encrypt Renewal Timer initialized [1/28/2021] [10:52:10 PM] [SSL ] › ℹ info Renewing SSL certs close to expiry... [1/28/2021] [10:52:10 PM] [IP Ranges] › ℹ info IP Ranges Renewal Timer initialized [1/28/2021] [10:52:10 PM] [Global ] › ℹ info Backend PID 657 listening on port 3000 ... [1/28/2021] [10:52:11 PM] [Nginx ] › ℹ info Reloading Nginx [1/28/2021] [10:52:11 PM] [SSL ] › ℹ info Renew Complete `QueryBuilder#allowEager` method is deprecated. You should use `allowGraph` instead. `allowEager` method will be removed in 3.0 `QueryBuilder#eager` method is deprecated. You should use the `withGraphFetched` method instead. `eager` method will be removed in 3.0 QueryBuilder#omit is deprecated. This method will be removed in version 3.0
  2. Has anyone been able to get the discord bot API working with Shinobi set up this way? I tried following the instructions listed here https://hub.shinobi.video/articles/view/Vx8KOsrUXTZxsSp and assumed that I could skip the step 'Enable Discord Bot use in Shinobi' because it looks like that option is now baked into the web UI, but after following the instructions the bot doesn't seem to come online.