H
Homarr•3d ago
Felaxo

Icons loading weirdly / websockets failing

I have added icons from both svg and png. In the Apps tab of the management panel, they load correctly. I have also noted that websocket requests are failing. i do not know, if those two issues come in hand, so i also attached the console log. The Homarr logs (/Tools/Logs) show up as just black (i presume that is since they would be streamed by wss). The Update Icons Task does nothing, or at least does not show any visual feedback. When creating an App, the Icon selector is stuck in the skeleton loading animation. For context: I have homarr set up on Ubuntu 24.04 (noble?), run it by docker compose plugin behind an nginx reverse proxy. homarr version: 1.18.0 Docker compose 
#---------------------------------------------------------------------#
#     Homarr - A simple, yet powerful dashboard for your server.      #
#---------------------------------------------------------------------#
services:
  homarr:
    container_name: homarr
    image: ghcr.io/homarr-labs/homarr:latest
    restart: unless-stopped
    volumes:
      - /var/run/docker.sock:/var/run/docker.sock # Optional, only if you want docker integration
      - ./homarr/appdata:/appdata
    environment:
      - SECRET_ENCRYPTION_KEY=<Redacted, generated via homarr docs>
    ports:
      - '7575:7575'
#---------------------------------------------------------------------#
#     Homarr - A simple, yet powerful dashboard for your server.      #
#---------------------------------------------------------------------#
services:
  homarr:
    container_name: homarr
    image: ghcr.io/homarr-labs/homarr:latest
    restart: unless-stopped
    volumes:
      - /var/run/docker.sock:/var/run/docker.sock # Optional, only if you want docker integration
      - ./homarr/appdata:/appdata
    environment:
      - SECRET_ENCRYPTION_KEY=<Redacted, generated via homarr docs>
    ports:
      - '7575:7575'
NGINX Conf 
server {
    listen 80;
    listen [::]:80;
    server_name home.<Redacted>;

    location / {
        return 301 https://$host$request_uri;
    }
}

server {
    listen 443 ssl;
    listen [::]:443 ssl;
    server_name home.<Redacted>;

    ssl_certificate /etc/letsencrypt/live/home.<Redacted>/fullchain.pem; # managed by Certbot
    ssl_certificate_key /etc/letsencrypt/live/home.<Redacted>/privkey.pem; # managed by Certbot
    include /etc/letsencrypt/options-ssl-nginx.conf; # managed by Certbot
    ssl_dhparam /etc/letsencrypt/ssl-dhparams.pem; # managed by Certbot

    location / {
    proxy_pass              http://127.0.0.1:7575;
    proxy_http_version      1.1;
    proxy_set_header        Upgrade $http_upgrade;
    proxy_set_header        Connection "upgrade";
    proxy_set_header        Host $host;
    proxy_set_header        X-Real-IP $remote_addr;
    proxy_set_header        X-Forwarded-For $proxy_add_x_forwarded_for;
    proxy_set_header        X-Forwarded-Proto $scheme;

    proxy_read_timeout      86400;
    proxy_send_timeout      86400;
    proxy_connect_timeout   86400;
    client_max_body_size    0;
    }
}
server {
    listen 80;
    listen [::]:80;
    server_name home.<Redacted>;

    location / {
        return 301 https://$host$request_uri;
    }
}

server {
    listen 443 ssl;
    listen [::]:443 ssl;
    server_name home.<Redacted>;

    ssl_certificate /etc/letsencrypt/live/home.<Redacted>/fullchain.pem; # managed by Certbot
    ssl_certificate_key /etc/letsencrypt/live/home.<Redacted>/privkey.pem; # managed by Certbot
    include /etc/letsencrypt/options-ssl-nginx.conf; # managed by Certbot
    ssl_dhparam /etc/letsencrypt/ssl-dhparams.pem; # managed by Certbot

    location / {
    proxy_pass              http://127.0.0.1:7575;
    proxy_http_version      1.1;
    proxy_set_header        Upgrade $http_upgrade;
    proxy_set_header        Connection "upgrade";
    proxy_set_header        Host $host;
    proxy_set_header        X-Real-IP $remote_addr;
    proxy_set_header        X-Forwarded-For $proxy_add_x_forwarded_for;
    proxy_set_header        X-Forwarded-Proto $scheme;

    proxy_read_timeout      86400;
    proxy_send_timeout      86400;
    proxy_connect_timeout   86400;
    client_max_body_size    0;
    }
}
Docker Logs (I have only attached the entries marked as error) 
20:M 27 Apr 2025 10:04:09.367 * Ready to accept connections tcp
homarr  |    ▲ Next.js 15.3.1
homarr  |    - Local:        http://afdd9790eb02:3000
homarr  |    - Network:      http://afdd9790eb02:3000
homarr  | 
homarr  |  ✓ Starting...
homarr  |  ✓ Ready in 1167ms
homarr  | node:internal/modules/cjs/loader:1404
homarr  |   throw err;
homarr  |   ^
homarr  | 
homarr  | Error: Cannot find module 'http-cookie-agent/http'
homarr  | Require stack:
homarr  | - /app/apps/tasks/tasks.cjs
homarr  |     at Function._resolveFilename (node:internal/modules/cjs/loader:1401:15)
homarr  |     at defaultResolveImpl (node:internal/modules/cjs/loader:1057:19)
homarr  |     at resolveForCJSWithHooks (node:internal/modules/cjs/loader:1062:22)
homarr  |     at Function._load (node:internal/modules/cjs/loader:1211:37)
homarr  |     at TracingChannel.traceSync (node:diagnostics_channel:322:14)
homarr  |     at wrapModuleLoad (node:internal/modules/cjs/loader:235:24)
homarr  |     at Module.require (node:internal/modules/cjs/loader:1487:12)
homarr  |     at require (node:internal/modules/helpers:135:16)
homarr  |     at ../../node_modules/node-unifi/unifi.js (/app/apps/tasks/tasks.cjs:160335:49)
homarr  |     at __require (/app/apps/tasks/tasks.cjs:17:50) {
homarr  |   code: 'MODULE_NOT_FOUND',
homarr  |   requireStack: [ '/app/apps/tasks/tasks.cjs' ]
homarr  | }
homarr  | 
homarr  | Node.js v22.15.0
20:M 27 Apr 2025 10:04:09.367 * Ready to accept connections tcp
homarr  |    ▲ Next.js 15.3.1
homarr  |    - Local:        http://afdd9790eb02:3000
homarr  |    - Network:      http://afdd9790eb02:3000
homarr  | 
homarr  |  ✓ Starting...
homarr  |  ✓ Ready in 1167ms
homarr  | node:internal/modules/cjs/loader:1404
homarr  |   throw err;
homarr  |   ^
homarr  | 
homarr  | Error: Cannot find module 'http-cookie-agent/http'
homarr  | Require stack:
homarr  | - /app/apps/tasks/tasks.cjs
homarr  |     at Function._resolveFilename (node:internal/modules/cjs/loader:1401:15)
homarr  |     at defaultResolveImpl (node:internal/modules/cjs/loader:1057:19)
homarr  |     at resolveForCJSWithHooks (node:internal/modules/cjs/loader:1062:22)
homarr  |     at Function._load (node:internal/modules/cjs/loader:1211:37)
homarr  |     at TracingChannel.traceSync (node:diagnostics_channel:322:14)
homarr  |     at wrapModuleLoad (node:internal/modules/cjs/loader:235:24)
homarr  |     at Module.require (node:internal/modules/cjs/loader:1487:12)
homarr  |     at require (node:internal/modules/helpers:135:16)
homarr  |     at ../../node_modules/node-unifi/unifi.js (/app/apps/tasks/tasks.cjs:160335:49)
homarr  |     at __require (/app/apps/tasks/tasks.cjs:17:50) {
homarr  |   code: 'MODULE_NOT_FOUND',
homarr  |   requireStack: [ '/app/apps/tasks/tasks.cjs' ]
homarr  | }
homarr  | 
homarr  | Node.js v22.15.0
I have not modified the image in any way.
No description
No description
No description
No description
Solution:
See https://github.com/homarr-labs/homarr/issues/2960, this a known issue with 1.18.0 Downgrade or wait for us to fix this bug.
Jump to solution
7 Replies
Cakey Bot
Cakey Bot•3d ago
Thank you for submitting a support request. Depending on the volume of requests, our team should get in contact with you shortly.
⚠️ Please include the following details in your post or we may reject your request without further comment: - Log (See https://homarr.dev/docs/community/faq#how-do-i-open-the-console--log) - Operating system (Unraid, TrueNAS, Ubuntu, ...) - Exact Homarr version (eg. 0.15.0, not latest) - Configuration (eg. docker-compose, screenshot or similar. Use ``your-text`` to format) - Other relevant information (eg. your devices, your browser, ...)
Frequently Asked Questions | Homarr documentation
Can I install Homarr on a Raspberry Pi?
Felaxo
FelaxoOP•3d ago
I guess, the tasks not working is caused by the error in the attached docker logs.
Solution
Manicraft1001
Manicraft1001•3d ago
See https://github.com/homarr-labs/homarr/issues/2960, this a known issue with 1.18.0 Downgrade or wait for us to fix this bug.
Felaxo
FelaxoOP•3d ago
this doesnt fix the issue i had with icons. i have upgraded to 1.18.1
Manicraft1001
Manicraft1001•3d ago
It might be a separate issue. We're still on it
Felaxo
FelaxoOP•3d ago
just saying because you marked this as solved
Meierschlumpf
Meierschlumpf•2d ago
Can you post updated logs? Do your logs contain a statement of updating the icons when starting it? Also do you see anything relevant in the network tab / logs in general when you try to search for icons?

Did you find this page helpful?