Closed krosseyed closed 2 months ago
Same here, the new update broke npm. Login is broken and dns challenge errors all time.
This is caused by various checks initiated during startup versus after the app has loaded. I'm filing a separate but related bug which sheds some light into the issue at hand.
There was another issue I discovered and it was related to how much RAM I allowed the VM to use. I am going to close this ticket for now as I am no longer trying to use NginxProxyManager for my homelab needs.
Just an update, ran this same setup on a brand new CRS2116 and it works fine. It was the RAM limit that got me on this bug.
Checklist
jc21/nginx-proxy-manager:latest
docker image?Describe the bug I cannot log into the admin interface after deploying a fresh v2.11.1 container on a Mikrotik CHR on AWS using a t3.micro.
To Reproduce Steps to reproduce the behavior:
Expected behavior To be able to log into the admin console. Not get a 502/Bad Gateway error
Screenshots
Operating System Mikrotik CHR v7.12.1 using the container application provided by Mikrotik
Additional context
I am getting in my logs the following output:
Using Sqlite: /data/database.sqlite
I know Mikrotik's RouterOS is not a popular platform, but it would be nice to have this configuration to run NPM documented somewhere so people who want to run this on RouterOS can do so. The newer hardware is definitely equivalent or faster than a RaspberryPi and has more networking capabilities than most computing platforms.