Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Got issues now accessing my heimdall #1434

Open
andymarden opened this issue Feb 20, 2025 · 1 comment
Open

Got issues now accessing my heimdall #1434

andymarden opened this issue Feb 20, 2025 · 1 comment

Comments

@andymarden
Copy link

It was working fine for months and now I get the browser hanging for ages, sometimes quick sometime very slow and sometimes errors out.

Example F12 from Edge:

BlockingPageContent.js:2  action SET_STORAGE_DATA @ 07:44:05.468
BlockingPageContent.js:2  prev state Object
BlockingPageContent.js:2  action     Object
BlockingPageContent.js:2  next state Object
web-client-content-script.js:2  Uncaught (in promise) Error: Access to storage is not allowed from this context.
NotificationContent.js:2  action SET_LOCALE @ 07:44:05.490
NotificationContent.js:2  prev state Object
NotificationContent.js:2  action     Object
NotificationContent.js:2  next state Object
NotificationContent.js:2  action SET_STORAGE_DATA @ 07:44:05.501
NotificationContent.js:2  prev state Object
NotificationContent.js:2  action     Object
NotificationContent.js:2  next state Object

        
        Failed to load resource: the server responded with a status of 500 (Internal Server Error)
app.js?id=3b306fb20ef1a3c96c09963a4f6ff712:1  Error: Network response was not ok: 500
    at app.js?id=3b306fb20ef1a3c96c09963a4f6ff712:1:147140
(anonymous) @ app.js?id=3b306fb20ef1a3c96c09963a4f6ff712:1
55:1 
        
        
        Failed to load resource: the server responded with a status of 500 (Internal Server Error)
app.js?id=3b306fb20ef1a3c96c09963a4f6ff712:1  Error: Network response was not ok: 500
    at app.js?id=3b306fb20ef1a3c96c09963a4f6ff712:1:147140
(anonymous) @ app.js?id=3b306fb20ef1a3c96c09963a4f6ff712:1

Where are the server logs? What portainer shows under logs is just the embedded nginx startup it seems:

[migrations] started

[migrations] 01-nginx-site-confs-default: skipped

[migrations] 02-default-location: skipped

[migrations] done

usermod: no changes

───────────────────────────────────────

      ██╗     ███████╗██╗ ██████╗

      ██║     ██╔════╝██║██╔═══██╗

      ██║     ███████╗██║██║   ██║

      ██║     ╚════██║██║██║   ██║

      ███████╗███████║██║╚██████╔╝

      ╚══════╝╚══════╝╚═╝ ╚═════╝

   Brought to you by linuxserver.io

───────────────────────────────────────

To support LSIO projects visit:

https://www.linuxserver.io/donate/

───────────────────────────────────────

GID/UID

───────────────────────────────────────

User UID:    911

User GID:    911

───────────────────────────────────────

Linuxserver.io version: v2.6.3-ls300

Build-date: 2025-02-14T18:41:55+00:00

───────────────────────────────────────

    

using keys found in /config/keys

**** The following active confs have different version dates than the samples that are shipped. ****

**** This may be due to user customization or an update to the samples. ****

**** You should compare the following files to the samples in the same folder and update them. ****

**** Use the link at the top of the file to view the changelog. ****

┌────────────┬────────────┬────────────────────────────────────────────────────────────────────────┐

│  old date  │  new date  │ path                                                                   │

├────────────┼────────────┼────────────────────────────────────────────────────────────────────────┤

│ 2023-04-13 │ 2024-05-27 │ /config/nginx/nginx.conf                                               │

│ 2023-04-13 │ 2024-07-16 │ /config/nginx/site-confs/default.conf                                  │

└────────────┴────────────┴────────────────────────────────────────────────────────────────────────┘

[custom-init] No custom files found, skipping...

nginx: [warn] the "listen ... http2" directive is deprecated, use the "http2" directive instead in /config/nginx/site-confs/default.conf:7

nginx: [warn] the "listen ... http2" directive is deprecated, use the "http2" directive instead in /config/nginx/site-confs/default.conf:8

[ls.io-init] done.

Can't see anything useful in the other logs - php, nginx and there is nothing under log/heimdall. I took my own reverse proxy out of the loop and still the same problems.

@andymarden
Copy link
Author

Now that's weird - I created another heimdall docker container and copied over the whole /config/www dir (bind mount on host). That works fine.

The only explanation I can think if is that something got corrupted in the other persistent subdirs of /config.

So I am back working again but I would like to know what happened.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Status: Non-Docker Issues
Development

No branches or pull requests

1 participant