Admin server can not save changes, error: 413 (Payload Too Large) and 404 (Not Found) #2703
Replies: 2 comments 4 replies
-
|
I think you are doing the right thing when you get the 413, the problem is on our end. We need to increase the payload size of the As for not being able to view the tracks while accessing the admin server port, it looks like you're running |
Beta Was this translation helpful? Give feedback.
-
|
FYI I've put in a PR to increase the payload size here: #2705 |
Beta Was this translation helpful? Give feedback.
-
|
thanks! I tested with another jbrowse installed with only 1 track and a small 3k config.json file. the admin server can now save the changes. Looking forward to the update to fix the max size! Running the admin server from the /var/www/html directory as suggested indeed solved the track viewing problem in admin mode. |
Beta Was this translation helpful? Give feedback.
-
|
New 1.6.5 release has this fix! |
Beta Was this translation helpful? Give feedback.
-
|
Dear Colin
Thanks for the fix!
I first run jbrowse upgrade and check the website’s help. It shows the version is 1.6.5 now. But when I use the admin-server, it still shows the same Payload too large error.
I also try to specify the body size limit but it doesn’t seem to be working.
***@***.***:/var/www/html$ jbrowse admin-server --target ./jbrowse2/config.json --bodySizeLimit 20mb
› Error: Unexpected arguments: --bodySizeLimit, 20mb
› See more help with --help
I also tried to reboot my webserver. Still not working. Is there something I need to do after upgrade to get the admin-server to work?
sorry for the trouble.
silin
… 2022年2月19日 上午7:55，Colin Diesh ***@***.***> 写道：
New 1.6.5 release has this fix!
—
Reply to this email directly, view it on GitHub <#2703 (reply in thread)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AKM7JMDYN5UJZLI3XF2H653U33MA3ANCNFSM5NISMN3A>.
Triage notifications on the go with GitHub Mobile for iOS <https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675> or Android <https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>.
You are receiving this because you authored the thread.
|
Beta Was this translation helpful? Give feedback.
-
|
Hi @silinzhong you will also want to upgrade the @jbrowse/cli tool. Try running |
Beta Was this translation helpful? Give feedback.
-
Hi
I don't know how to use the admin server to save the changes i made. I installed the jbrowse2 in /var/www/html/jbrowse2. i started the admin server using jbrowse admin-server --target=config.json
If i login using the ip address followed by the port like 137.189.43.55:9090?adminKey=xxxxx and make some changes, i will get the 413 (Payload Too Large) err at the bottom on the track screen, as well as an error on the terminal.
If i login using the ip address without using the port 9090 like 137.189.43.55/jbrowse2?adminKey=xxxx and make changes, i will get the 404 (Not Found) err message.
I might have done something wrong with the add tracks as well. I put the bigwig files in the folder /var/www/html/SSD/... I then add the tracks using jbrowse add-track /SSD/Mp/xxx.bw -a ".." -n "..." --load inPlace --force. I can view the tracks when accessing the jbrowse using 137.189.43.55/jbrowse2. If i open the Jbrowse using 137.189.43.55:9090 (no matter with or w/o adminKey), it can not load the bigwig file as it is trying to find it at 137.189.43.55:9090/SSD/...
What should I do?
error message displayed on laptop's chrome jbrowse2 screen
Admin server error: 413 (Payload Too Large) <title>Error</title>
error message display on the web server terminal
PayloadTooLargeError: request entity too large
at readStream (/usr/local/lib/node_modules/@jbrowse/cli/node_modules/raw-body/index.js:155:17)
at getRawBody (/usr/local/lib/node_modules/@jbrowse/cli/node_modules/raw-body/index.js:108:12)
at read (/usr/local/lib/node_modules/@jbrowse/cli/node_modules/body-parser/lib/read.js:77:3)
at jsonParser (/usr/local/lib/node_modules/@jbrowse/cli/node_modules/body-parser/lib/types/json.js:135:5)
at Layer.handle [as handle_request] (/usr/local/lib/node_modules/@jbrowse/cli/node_modules/express/lib/router/layer.js:95:5)
at trim_prefix (/usr/local/lib/node_modules/@jbrowse/cli/node_modules/express/lib/router/index.js:323:13)
at /usr/local/lib/node_modules/@jbrowse/cli/node_modules/express/lib/router/index.js:284:7
at Function.process_params (/usr/local/lib/node_modules/@jbrowse/cli/node_modules/express/lib/router/index.js:341:12)
at next (/usr/local/lib/node_modules/@jbrowse/cli/node_modules/express/lib/router/index.js:275:10)
at cors (/usr/local/lib/node_modules/@jbrowse/cli/node_modules/cors/lib/index.js:188:7)
error message when login using 137.189.43.55/jbrowse2/
Admin server error: 404 (Not Found) <title>404 Not Found</title>
Not Found
The requested URL was not found on this server.
Apache/2.4.41 (Ubuntu) Server at 137.189.43.55 Port 80
Beta Was this translation helpful? Give feedback.
All reactions