github-starred/actual
2
0
Fork 0
mirror of https://github.com/actualbudget/actual.git synced 2026-07-22 15:19:25 -05:00
Code Issues 3.0k Packages Projects Releases 58 Wiki Activity

[GH-ISSUE #4764] [Bug]: Rejection: TypeError: invalid IP address: 10.0.222.222 #51149

New Issue
Closed
opened 2026-04-30 17:02:55 -05:00 by GiteaMirror · 1 comment
GiteaMirror commented 2026-04-30 17:02:55 -05:00
Owner
Copy Link
Copy Source

Originally created by @raldone01 on GitHub (Apr 7, 2025).
Original GitHub issue: https://github.com/actualbudget/actual/issues/4764

What happened?

Previously this configuration was working.
The ip in question looks pretty valid to me.
Maybe there is some whitespace around it?

actual_server-1  | Checking if there are any migrations to run for direction "up"...
actual_server-1  | Migrations: DONE
actual_server-1  | Rejection: TypeError: invalid IP address:  10.0.222.222
actual_server-1  |     at parseipNotation (/app/node_modules/proxy-addr/index.js:163:11)
actual_server-1  |     at compileRangeSubnets (/app/node_modules/proxy-addr/index.js:126:23)
actual_server-1  |     at Function.compile (/app/node_modules/proxy-addr/index.js:112:23)
actual_server-1  |     at exports.compileTrust (/app/node_modules/express/lib/utils.js:234:20)
actual_server-1  |     at Function.set (/app/node_modules/express/lib/application.js:389:34)
actual_server-1  |     at file:///app/src/app.js:28:5
actual_server-1  | Checking if there are any migrations to run for direction "up"...
actual_server-1  | Migrations: DONE
actual_server-1  | Rejection: TypeError: invalid IP address:  10.0.222.222
actual_server-1  |     at parseipNotation (/app/node_modules/proxy-addr/index.js:163:11)
actual_server-1  |     at compileRangeSubnets (/app/node_modules/proxy-addr/index.js:126:23)
actual_server-1  |     at Function.compile (/app/node_modules/proxy-addr/index.js:112:23)
actual_server-1  |     at exports.compileTrust (/app/node_modules/express/lib/utils.js:234:20)
actual_server-1  |     at Function.set (/app/node_modules/express/lib/application.js:389:34)
actual_server-1  |     at file:///app/src/app.js:28:5
actual_server-1  | Checking if there are any migrations to run for direction "up"...
actual_server-1  | Migrations: DONE

How can we reproduce the issue?

services:
  actual_server:
    extends:
      file: docker-compose-extends.yml
      service: base_service
    image: docker.io/actualbudget/actual-server:latest
    #ports:
      #- '5006:5006'
    environment:
      - ACTUAL_TRUSTED_PROXIES=2a02:redacted:redacted:redacted:redacted:redacted:redacted:redacted/128, 10.0.222.222/32
      # Uncomment any of the lines below to set configuration options.
      # - ACTUAL_HTTPS_KEY=/data/selfhost.key
      # - ACTUAL_HTTPS_CERT=/data/selfhost.crt
      # - ACTUAL_PORT=5006
      # - ACTUAL_UPLOAD_FILE_SYNC_SIZE_LIMIT_MB=20
      # - ACTUAL_UPLOAD_SYNC_ENCRYPTED_FILE_SYNC_SIZE_LIMIT_MB=50
      # - ACTUAL_UPLOAD_FILE_SIZE_LIMIT_MB=20
      # See all options and more details at https://actualbudget.github.io/docs/Installing/Configuration
      # !! If you are not using any of these options, remove the 'environment:' tag entirely.
    volumes:
      - ${CONTAINER_SSD}/comp_actual/data:/data
    networks:
      behind-nginx-ip:
          ipv4_address: 10.0.222.13

Where are you hosting Actual?

Docker

What browsers are you seeing the problem on?

Other

Operating System

Linux

Originally created by @raldone01 on GitHub (Apr 7, 2025). Original GitHub issue: https://github.com/actualbudget/actual/issues/4764 ### What happened? Previously this configuration was working. The ip in question looks pretty valid to me. Maybe there is some whitespace around it? ``` actual_server-1 | Checking if there are any migrations to run for direction "up"... actual_server-1 | Migrations: DONE actual_server-1 | Rejection: TypeError: invalid IP address: 10.0.222.222 actual_server-1 | at parseipNotation (/app/node_modules/proxy-addr/index.js:163:11) actual_server-1 | at compileRangeSubnets (/app/node_modules/proxy-addr/index.js:126:23) actual_server-1 | at Function.compile (/app/node_modules/proxy-addr/index.js:112:23) actual_server-1 | at exports.compileTrust (/app/node_modules/express/lib/utils.js:234:20) actual_server-1 | at Function.set (/app/node_modules/express/lib/application.js:389:34) actual_server-1 | at file:///app/src/app.js:28:5 actual_server-1 | Checking if there are any migrations to run for direction "up"... actual_server-1 | Migrations: DONE actual_server-1 | Rejection: TypeError: invalid IP address: 10.0.222.222 actual_server-1 | at parseipNotation (/app/node_modules/proxy-addr/index.js:163:11) actual_server-1 | at compileRangeSubnets (/app/node_modules/proxy-addr/index.js:126:23) actual_server-1 | at Function.compile (/app/node_modules/proxy-addr/index.js:112:23) actual_server-1 | at exports.compileTrust (/app/node_modules/express/lib/utils.js:234:20) actual_server-1 | at Function.set (/app/node_modules/express/lib/application.js:389:34) actual_server-1 | at file:///app/src/app.js:28:5 actual_server-1 | Checking if there are any migrations to run for direction "up"... actual_server-1 | Migrations: DONE ``` ### How can we reproduce the issue? ```yml services: actual_server: extends: file: docker-compose-extends.yml service: base_service image: docker.io/actualbudget/actual-server:latest #ports: #- '5006:5006' environment: - ACTUAL_TRUSTED_PROXIES=2a02:redacted:redacted:redacted:redacted:redacted:redacted:redacted/128, 10.0.222.222/32 # Uncomment any of the lines below to set configuration options. # - ACTUAL_HTTPS_KEY=/data/selfhost.key # - ACTUAL_HTTPS_CERT=/data/selfhost.crt # - ACTUAL_PORT=5006 # - ACTUAL_UPLOAD_FILE_SYNC_SIZE_LIMIT_MB=20 # - ACTUAL_UPLOAD_SYNC_ENCRYPTED_FILE_SYNC_SIZE_LIMIT_MB=50 # - ACTUAL_UPLOAD_FILE_SIZE_LIMIT_MB=20 # See all options and more details at https://actualbudget.github.io/docs/Installing/Configuration # !! If you are not using any of these options, remove the 'environment:' tag entirely. volumes: - ${CONTAINER_SSD}/comp_actual/data:/data networks: behind-nginx-ip: ipv4_address: 10.0.222.13 ``` ### Where are you hosting Actual? Docker ### What browsers are you seeing the problem on? Other ### Operating System Linux
GiteaMirror added the bug label 2026-04-30 17:02:55 -05:00
GiteaMirror commented 2026-04-30 17:02:56 -05:00
Author
Owner
Copy Link
Copy Source

@raldone01 commented on GitHub (Apr 7, 2025):

How to fix

Reintroduce a trim before passing along the ip string.

<!-- gh-comment-id:2783882858 --> @raldone01 commented on GitHub (Apr 7, 2025): ### How to fix Reintroduce a trim before passing along the ip string.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
AI generated
API
bank sync
budgeting
bug
can’t replicate
dependencies
docker
documentation
electron
experimental feature
feature
feedback
goal templates
good first issue
help wanted
importers
maintenance
needs info
needs testing
needs triage
needs votes
openid
payees
pull-request
Mirrored from GitHub Pull Request
 regression
reports
responsive
rules
schedules
server
✨ merged
split transactions
tech debt
tech-support
theme
transaction import
transaction reconciliation
transactions
translations
upstream
user interface
✅ approved
wontfix
No labels bug
Milestone
No items
No Milestone
Projects
Clear projects
No projects
Assignees
Clear assignees
GiteaMirror ninjasurge (Kaehlen Rog)
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/actual#51149