"The connection was reset" on add user page
Just installed this and set myself up as the admin user. Added an item to my list just fine.
Decided to add a user so I went to Admin Settings and hit the Add User button. It navigates to http://192.168.1.5:8082/admin-settings/add and I get a The connection was reset error every single time.
I'm seeing this in the log:
Node.js v20.19.3
node:internal/process/promises:391
triggerUncaughtException(err, true /* fromPromise */);
^
Error
at new CustomPouchError (/usr/src/app/node_modules/pouchdb/lib/index.js:656:21)
at createError (/usr/src/app/node_modules/pouchdb/lib/index.js:665:10)
at updateDoc (/usr/src/app/node_modules/pouchdb/lib/index.js:4621:15)
at nextDoc (/usr/src/app/node_modules/pouchdb/lib/index.js:4740:9)
at /usr/src/app/node_modules/pouchdb/lib/index.js:4750:5
at Map.forEach (<anonymous>)
at processDocs (/usr/src/app/node_modules/pouchdb/lib/index.js:4724:13)
at /usr/src/app/node_modules/pouchdb/lib/index.js:5650:9
at checkDone (/usr/src/app/node_modules/pouchdb/lib/index.js:5331:18)
at /usr/src/app/node_modules/pouchdb/lib/index.js:5349:11 {
status: 409,
name: 'conflict',
message: 'Document update conflict',
error: true,
id: '<redacted>',
docId: '<redacted>'
}
Node.js v20.19.3
[ EXPRESS ] undefined - GET /admin-settings
[ EXPRESS ] ::ffff:192.168.1.50 - GET /
[ EXPRESS ] ::ffff:192.168.1.50 - GET /wishlist
[ EXPRESS ] ::ffff:192.168.1.50 - GET /libraries/bulmaswatch/default/bulmaswatch.min.css
[ EXPRESS ] ::ffff:192.168.1.50 - GET /libraries/fontawesome/css/all.css
[ EXPRESS ] ::ffff:192.168.1.50 - GET /libraries/animate.min.css
[ EXPRESS ] ::ffff:192.168.1.50 - GET /js/nav.js
[ EXPRESS ] ::ffff:192.168.1.50 - GET /css/main.css
[ EXPRESS ] ::ffff:192.168.1.50 - GET /img/logo.transparent.png
[ EXPRESS ] ::ffff:192.168.1.50 - GET /img/default-pfps/2.jpg
[ EXPRESS ] ::ffff:192.168.1.50 - GET /img/logo.png
[ EXPRESS ] ::ffff:192.168.1.50 - GET /wishlist/<redacted>
[ EXPRESS ] ::ffff:192.168.1.50 - GET /libraries/bulmaswatch/default/bulmaswatch.min.css
[ EXPRESS ] ::ffff:192.168.1.50 - GET /libraries/fontawesome/css/all.css
[ EXPRESS ] ::ffff:192.168.1.50 - GET /css/main.css
[ EXPRESS ] ::ffff:192.168.1.50 - GET /libraries/animate.min.css
[ EXPRESS ] ::ffff:192.168.1.50 - GET /js/wishlist.js
[ EXPRESS ] ::ffff:192.168.1.50 - GET /js/nav.js
[ EXPRESS ] ::ffff:192.168.1.50 - GET /img/logo.transparent.png
[ EXPRESS ] ::ffff:192.168.1.50 - GET /libraries/fontawesome/webfonts/fa-regular-400.woff2
[ EXPRESS ] ::ffff:192.168.1.50 - GET /admin-settings
[ EXPRESS ] ::ffff:192.168.1.50 - GET /js/nav.js
[ EXPRESS ] ::ffff:192.168.1.50 - GET /css/main.css
[ EXPRESS ] ::ffff:192.168.1.50 - GET /libraries/bulmaswatch/default/bulmaswatch.min.css
[ EXPRESS ] ::ffff:192.168.1.50 - GET /libraries/fontawesome/css/all.css
[ EXPRESS ] ::ffff:192.168.1.50 - GET /libraries/animate.min.css
[ EXPRESS ] ::ffff:192.168.1.50 - GET /img/logo.transparent.png
[ EXPRESS ] ::ffff:192.168.1.50 - GET /img/logo.png
[ EXPRESS ] ::ffff:192.168.1.50 - POST /admin-settings/add
[ EXPRESS ] Express server started on port 80!
[ EXPRESS ] ::ffff:192.168.1.50 - POST /admin-settings/add
[ EXPRESS ] Express server started on port 80!
I'm running UNRAID 7.1.4 and installed the container via Community Apps from grtgbln's repository. The only change I made from the template defaults was to the WebUI Port, changing it to 8082, since I've already got several others in use around there, and port 80 is in use, as well.
Version Info from the Admin page:
Christmas Community: v1.41.0
Get Product Data: v1.19.0
Node: v20.19.3
PID: 98
@daFreeMan - I think that this might be an issue with the unraid image and the defaults it sets. I sounds like it's a similar issue to that experienced in #134. If you can use compose on unraid (I don't use the platform), then try with the example in the README in the first instance and let us know how you get on.
@cj13579 I believe this is the one you were referring to: https://github.com/Wingysam/Christmas-Community/issues/134#issuecomment-2380658548
I've added the /login to the WebUI port and to the login failure redirect and still end up at the main page.
Here are the parameters I'm setting - maybe I didn't get something quite right?
docker run
-d
--name='Christmas-Community'
--net='bridge'
--pids-limit 2048
-e TZ="America/New_York"
-e HOST_OS="Unraid"
-e HOST_HOSTNAME="NAS"
-e HOST_CONTAINERNAME="Christmas-Community"
-e 'LISTS_PUBLIC'='false'
-e 'SINGLE_LIST'='false'
-e 'TABLE'='true'
-e 'SITE_TITLE'='Christmas Community'
-e 'SHORT_TITLE'='Christmas'
-e 'MARKDOWN'='true'
-e 'UPDATE_CHECK'='true'
-e 'PFP'='true'
-e 'BULMASWATCH'='default'
-e 'DB_PREFIX'='/data/dbs'
-e 'PORT'='80'
-e 'DB_EXPOSE_PORT'=''
-e 'PROXY_SERVER'=''
-e 'SECRET'=''
-e 'MAX_AGE'='604800000'
-e 'ROOT_PATH'='/'
-e 'DEFAULT_FAILURE_REDIRECT'='/login'
-e 'TRUST_PROXY'='loopback'
-e 'SMILE'='false'
-e 'LANGUAGE'='en-US'
-l net.unraid.docker.managed=dockerman
-l net.unraid.docker.webui='http://[IP]:[PORT:80]/login'
-l net.unraid.docker.icon='https://raw.githubusercontent.com/Wingysam/Christmas-Community/master/src/static/img/logo.transparent.png'
-p '8082:8082/tcp'
-v '/mnt/user/appdata/christmas_community/data':'/data':'rw' 'wingysam/christmas-community:latest'
Right, back from vacation. I've run your command locally (I don't have unraid, just WSL) and I can't replicate it. The only thing that looks suspicious is this:
-l net.unraid.docker.webui='http://[IP]:[PORT:80]/login' \
What happens if you change that to just http://[IP]:[PORT:80]/
What happens if you change that to just
http://[IP]:[PORT:80]/
I think you mean this line:
I don't see that trailing backslash...
I don't see that trailing backslash...
That's not the important bit, so you can ignore that. The important bit is removing "login"
oh. gotcha. reading comprehension fail..
This is on UNRAID, so I'll have to see what I can do to manipulate that via the templates...
Got it edited. It defaults to port 80, which is UNRAID's gui.
Changed it to port 8082 and now it cannot establish a connection...
You just want to remove "login" from the end of the string. Don't change the port.
But if I don't change the port, I just get my unraid management UI. 192.168.1.5 is my UNRAID server. Has been for a decade...
OK, can you try updating the port option to -p 8082:80
OK, I've got it working now with this:
docker run
-d
--name='Christmas-Community'
--net='bridge'
--pids-limit 2048
-e TZ="America/New_York"
-e HOST_OS="Unraid"
-e HOST_HOSTNAME="NAS"
-e HOST_CONTAINERNAME="Christmas-Community"
-e 'LISTS_PUBLIC'='false'
-e 'SINGLE_LIST'='false'
-e 'TABLE'='true'
-e 'SITE_TITLE'='Christmas Community'
-e 'SHORT_TITLE'='Christmas'
-e 'MARKDOWN'='true'
-e 'UPDATE_CHECK'='true'
-e 'PFP'='true'
-e 'BULMASWATCH'='default'
-e 'DB_PREFIX'='/data/dbs'
-e 'PORT'='8082'
-e 'DB_EXPOSE_PORT'=''
-e 'PROXY_SERVER'=''
-e 'SECRET'=''
-e 'MAX_AGE'='604800000'
-e 'ROOT_PATH'='/'
-e 'DEFAULT_FAILURE_REDIRECT'='/'
-e 'TRUST_PROXY'='loopback'
-e 'SMILE'='false'
-e 'LANGUAGE'='en-US'
-l net.unraid.docker.managed=dockerman
-l net.unraid.docker.webui='http://[IP]:[PORT:8082]/'
-l net.unraid.docker.icon='https://raw.githubusercontent.com/Wingysam/Christmas-Community/master/src/static/img/logo.transparent.png'
-p '8082:8082/tcp'
-v '/mnt/user/appdata/christmas_community/data':'/data':'rw' 'wingysam/christmas-community:latest'
065a96eba133041d0d1faa53d2458b8bb523d547a31026059eecb855c1ae2375
Now back to the originally scheduled issue: I try to add another user and I get a "connection was reset" at http://192.168.1.5:8082/admin-settings/add.