Cloudron makes it easy to run web apps like WordPress, Nextcloud, GitLab on your server. Find out more or install now.


Skip to content
  • Categories
  • Recent
  • Tags
  • Popular
  • Bookmarks
  • Search
Skins
  • Light
  • Brite
  • Cerulean
  • Cosmo
  • Flatly
  • Journal
  • Litera
  • Lumen
  • Lux
  • Materia
  • Minty
  • Morph
  • Pulse
  • Sandstone
  • Simplex
  • Sketchy
  • Spacelab
  • United
  • Yeti
  • Zephyr
  • Dark
  • Cyborg
  • Darkly
  • Quartz
  • Slate
  • Solar
  • Superhero
  • Vapor
  • Default (No Skin)
  • No Skin
Collapse
Brand Logo

Cloudron Forum
Apps - Status | Demo | Docs | Install
  1. Cloudron Forum
  2. Paperless-ngx
  3. 400 Bad Request error when trying to access documents vie GUI

400 Bad Request error when trying to access documents vie GUI

Scheduled Pinned Locked Moved Solved Paperless-ngx
6 Posts 3 Posters 1.6k Views 3 Watching
  • Oldest to Newest
  • Newest to Oldest
  • Most Votes
Reply
  • Reply as topic
Log in to reply
This topic has been deleted. Only users with topic management privileges can see it.
  • N Offline
    N Offline
    Nerdrelaxo
    wrote on last edited by
    #1

    Hi,

    I don't know exactly when it started, but I noticed it yesterday when the package 1.31.3 was the actual version and the package 1.31.4 didn't fix the error. When I click on Documents I get the following error:

    Fehler beim Laden der Dokumente: <html>
    <head><title>400 Bad Request</title></head>
    <body>
    <center><h1>400 Bad Request</h1></center>
    <hr><center>nginx</center>
    </body>
    </html>

    However accessing the documents with PaperParrot on my iPhone works.

    I tried restarting the container as well as the whole host. Any ideas? What happens when I use the repair option in Cloudron? Are all my settings and contents gone?

    Regards
    Hendrik

    J 1 Reply Last reply
    0
    • nebulonN Offline
      nebulonN Offline
      nebulon
      Staff
      wrote on last edited by
      #2

      Could it be some caching issue and do you see any errors on the server side if you check the app logs while trying to access those documents?

      N 1 Reply Last reply
      0
      • N Nerdrelaxo

        Hi,

        I don't know exactly when it started, but I noticed it yesterday when the package 1.31.3 was the actual version and the package 1.31.4 didn't fix the error. When I click on Documents I get the following error:

        Fehler beim Laden der Dokumente: <html>
        <head><title>400 Bad Request</title></head>
        <body>
        <center><h1>400 Bad Request</h1></center>
        <hr><center>nginx</center>
        </body>
        </html>

        However accessing the documents with PaperParrot on my iPhone works.

        I tried restarting the container as well as the whole host. Any ideas? What happens when I use the repair option in Cloudron? Are all my settings and contents gone?

        Regards
        Hendrik

        J Offline
        J Offline
        joseph
        Staff
        wrote on last edited by
        #3

        @Nerdrelaxo said in 400 Bad Request error when trying to access documents vie GUI:

        What happens when I use the repair option in Cloudron? Are all my settings and contents gone?

        repair is only putting the container in repair mode - https://docs.cloudron.io/apps/#recovery-mode . no data is lost. but this is probably not what you want to solve your problem.

        1 Reply Last reply
        0
        • nebulonN nebulon

          Could it be some caching issue and do you see any errors on the server side if you check the app logs while trying to access those documents?

          N Offline
          N Offline
          Nerdrelaxo
          wrote on last edited by
          #4

          @nebulon

          I don't see anything related in the logs when I try to access the documents.

          Jan 23 17:00:00 13:M 23 Jan 2025 16:00:00.155 * 10 changes in 300 seconds. Saving...
          Jan 23 17:00:00 13:M 23 Jan 2025 16:00:00.155 * Background saving started by pid 250
          Jan 23 17:00:00 13:M 23 Jan 2025 16:00:00.257 * Background saving terminated with success
          Jan 23 17:00:00 250:C 23 Jan 2025 16:00:00.159 * DB saved on disk
          Jan 23 17:00:00 250:C 23 Jan 2025 16:00:00.160 * Fork CoW for RDB: current 0 MB, peak 0 MB, average 0 MB
          Jan 23 17:00:00 [2025-01-23 16:00:00,066] [INFO] [celery.beat] Scheduler: Sending due task Check all e-mail accounts (paperless_mail.tasks.process_mail_accounts)
          Jan 23 17:00:00 [2025-01-23 16:00:00,069] [INFO] [celery.worker.strategy] Task paperless_mail.tasks.process_mail_accounts[b10dff4d-3c1e-4f39-8f3e-d55cd16e8e1d] received
          Jan 23 17:00:00 [2025-01-23 16:00:00,128] [INFO] [celery.app.trace] Task paperless_mail.tasks.process_mail_accounts[b10dff4d-3c1e-4f39-8f3e-d55cd16e8e1d] succeeded in 0.057467245002044365s: 'No new documents were added.'
          Jan 23 17:00:47 Running movescans
          Jan 23 17:00:47 mv: cannot stat '/media/Storagebox Scanner/*': No such file or directory
          Jan 23 17:05:00 [2025-01-23 16:05:00,054] [INFO] [celery.beat] Scheduler: Sending due task Train the classifier (documents.tasks.train_classifier)
          Jan 23 17:05:00 [2025-01-23 16:05:00,057] [INFO] [celery.beat] Scheduler: Sending due task Check and run scheduled workflows (documents.tasks.check_scheduled_workflows)
          Jan 23 17:05:00 [2025-01-23 16:05:00,057] [INFO] [celery.worker.strategy] Task documents.tasks.train_classifier[a584d8f6-2fe8-4e6a-969a-59073b8aacc6] received
          Jan 23 17:05:00 [2025-01-23 16:05:00,061] [INFO] [celery.worker.strategy] Task documents.tasks.check_scheduled_workflows[71079fb2-98ab-4433-86c0-93d6cd66e0ca] received
          Jan 23 17:05:01 13:M 23 Jan 2025 16:05:01.001 * 10 changes in 300 seconds. Saving...
          Jan 23 17:05:01 13:M 23 Jan 2025 16:05:01.002 * Background saving started by pid 251
          Jan 23 17:05:01 251:C 23 Jan 2025 16:05:01.005 * DB saved on disk
          Jan 23 17:05:01 251:C 23 Jan 2025 16:05:01.006 * Fork CoW for RDB: current 0 MB, peak 0 MB, average 0 MB
          Jan 23 17:05:01 13:M 23 Jan 2025 16:05:01.103 * Background saving terminated with success
          Jan 23 17:05:01 [2025-01-23 16:05:01,373] [INFO] [paperless.classifier] No updates since last training
          Jan 23 17:05:01 [2025-01-23 16:05:01,386] [INFO] [celery.app.trace] Task documents.tasks.train_classifier[a584d8f6-2fe8-4e6a-969a-59073b8aacc6] succeeded in 1.3244988239894155s: None
          Jan 23 17:05:01 [2025-01-23 16:05:01,774] [INFO] [celery.app.trace] Task documents.tasks.check_scheduled_workflows[71079fb2-98ab-4433-86c0-93d6cd66e0ca] succeeded in 0.0695804700080771s: None

          The movescans error is from a script that moves new scans from my scanner to the import directory. I wonder why the nginx errors are not in there. Also nothing in the box logs:

          Jan 23 17:00:00 box:eventlog cleanup: pruning events. creationTime: Fri Oct 25 2024 16:00:00 GMT+0000 (Coordinated Universal Time)
          Jan 23 17:00:00 box:janitor Cleaning up expired tokens
          Jan 23 17:00:00 box:janitor Cleaned up 0 expired tokens
          Jan 23 17:00:00 box:apphealthmonitor app health: 2 running / 0 stopped / 0 unresponsive
          Jan 23 17:00:10 box:apphealthmonitor app health: 2 running / 0 stopped / 0 unresponsive
          Jan 23 17:00:20 box:apphealthmonitor app health: 2 running / 0 stopped / 0 unresponsive
          Jan 23 17:00:30 box:apphealthmonitor app health: 2 running / 0 stopped / 0 unresponsive
          Jan 23 17:00:40 box:apphealthmonitor app health: 2 running / 0 stopped / 0 unresponsive
          Jan 23 17:00:50 box:apphealthmonitor app health: 2 running / 0 stopped / 0 unresponsive
          Jan 23 17:01:00 box:apphealthmonitor app health: 2 running / 0 stopped / 0 unresponsive
          Jan 23 17:01:10 box:apphealthmonitor app health: 2 running / 0 stopped / 0 unresponsive
          Jan 23 17:01:20 box:apphealthmonitor app health: 2 running / 0 stopped / 0 unresponsive
          Jan 23 17:01:30 box:apphealthmonitor app health: 2 running / 0 stopped / 0 unresponsive
          Jan 23 17:01:40 box:apphealthmonitor app health: 2 running / 0 stopped / 0 unresponsive
          Jan 23 17:01:50 box:apphealthmonitor app health: 2 running / 0 stopped / 0 unresponsive
          Jan 23 17:02:00 box:apphealthmonitor app health: 2 running / 0 stopped / 0 unresponsive
          Jan 23 17:02:10 box:apphealthmonitor app health: 2 running / 0 stopped / 0 unresponsive
          Jan 23 17:02:20 box:apphealthmonitor app health: 2 running / 0 stopped / 0 unresponsive
          Jan 23 17:02:30 box:apphealthmonitor app health: 2 running / 0 stopped / 0 unresponsive
          Jan 23 17:02:40 box:apphealthmonitor app health: 2 running / 0 stopped / 0 unresponsive
          Jan 23 17:02:50 box:apphealthmonitor app health: 2 running / 0 stopped / 0 unresponsive
          Jan 23 17:03:00 box:apphealthmonitor app health: 2 running / 0 stopped / 0 unresponsive
          Jan 23 17:03:10 box:apphealthmonitor app health: 2 running / 0 stopped / 0 unresponsive
          Jan 23 17:03:20 box:apphealthmonitor app health: 2 running / 0 stopped / 0 unresponsive
          Jan 23 17:03:30 box:apphealthmonitor app health: 2 running / 0 stopped / 0 unresponsive
          Jan 23 17:03:31 box:shell system: swapon --noheadings --raw --bytes --show=type,size,used,name
          Jan 23 17:03:40 box:apphealthmonitor app health: 2 running / 0 stopped / 0 unresponsive
          Jan 23 17:03:50 box:apphealthmonitor app health: 2 running / 0 stopped / 0 unresponsive
          Jan 23 17:04:00 box:apphealthmonitor app health: 2 running / 0 stopped / 0 unresponsive
          Jan 23 17:04:10 box:apphealthmonitor app health: 2 running / 0 stopped / 0 unresponsive
          Jan 23 17:04:20 box:apphealthmonitor app health: 2 running / 0 stopped / 0 unresponsive
          Jan 23 17:04:30 box:apphealthmonitor app health: 2 running / 0 stopped / 0 unresponsive
          Jan 23 17:04:40 box:apphealthmonitor app health: 2 running / 0 stopped / 0 unresponsive
          Jan 23 17:04:41 box:shell logs /usr/bin/sudo -S /home/yellowtent/box/src/scripts/logtail.sh --lines=100 --follow /home/yellowtent/platformdata/logs/8e3f77b8-0c99-49b8-b90c-decbb36c618e/apptask.log /home/yellowtent/platformdata/logs/8e3f77b8-0c99-49b8-b90c-decbb36c618e/app.log /home/yellowtent/platformdata/logs/redis-8e3f77b8-0c99-49b8-b90c-decbb36c618e/app.log
          Jan 23 17:04:41 box:shell tail: warning: --retry only effective for the initial open

          1 Reply Last reply
          0
          • N Offline
            N Offline
            Nerdrelaxo
            wrote on last edited by
            #5

            Okay, after all it was a browser issue. I deleted all website data in Safari and the error was gone. Sorry I bothered you.

            1 Reply Last reply
            0
            • nebulonN Offline
              nebulonN Offline
              nebulon
              Staff
              wrote on last edited by
              #6

              Glad it worked out in the end though!

              1 Reply Last reply
              0
              • nebulonN nebulon marked this topic as a question on
              • nebulonN nebulon has marked this topic as solved on

              Hello! It looks like you're interested in this conversation, but you don't have an account yet.

              Getting fed up of having to scroll through the same posts each visit? When you register for an account, you'll always come back to exactly where you were before, and choose to be notified of new replies (either via email, or push notification). You'll also be able to save bookmarks and upvote posts to show your appreciation to other community members.

              With your input, this post could be even better 💗

              Register Login
              Reply
              • Reply as topic
              Log in to reply
              • Oldest to Newest
              • Newest to Oldest
              • Most Votes

              • Login
              • Don't have an account? Register
              • Login or register to search.
              • First post
                Last post
              0
              • Categories
              • Recent
              • Tags
              • Popular
              • Bookmarks
              • Search