[Bug]: Actual Server Invalid IP address error #2025

Closed
opened 2026-02-28 20:01:26 -06:00 by GiteaMirror · 2 comments
Owner

Originally created by @cordlord on GitHub (Apr 7, 2025).

Verified issue does not already exist?

  • I have searched and found no existing issue

What happened?

I am running Actual server using the official Docker image.

After upgrading to version 25.4.0 from 25.3.1, I am receiving this error in the logs:

Checking if there are any migrations to run for direction "up"...

Migrations: DONE

Rejection: TypeError: invalid IP address:  172.16.0.0

    at parseipNotation (/app/node_modules/proxy-addr/index.js:163:11)

    at compileRangeSubnets (/app/node_modules/proxy-addr/index.js:126:23)

    at Function.compile (/app/node_modules/proxy-addr/index.js:112:23)

    at exports.compileTrust (/app/node_modules/express/lib/utils.js:234:20)

    at Function.set (/app/node_modules/express/lib/application.js:389:34)

    at file:///app/src/app.js:28:5

How can we reproduce the issue?

I am not sure what is causing this error, so I'm not sure how it could be reproduced.

Where are you hosting Actual?

Docker

What browsers are you seeing the problem on?

Desktop App (Electron)

Operating System

Linux

Originally created by @cordlord on GitHub (Apr 7, 2025). ### Verified issue does not already exist? - [x] I have searched and found no existing issue ### What happened? I am running Actual server using the official Docker image. After upgrading to version 25.4.0 from 25.3.1, I am receiving this error in the logs: ``` Checking if there are any migrations to run for direction "up"... Migrations: DONE Rejection: TypeError: invalid IP address: 172.16.0.0 at parseipNotation (/app/node_modules/proxy-addr/index.js:163:11) at compileRangeSubnets (/app/node_modules/proxy-addr/index.js:126:23) at Function.compile (/app/node_modules/proxy-addr/index.js:112:23) at exports.compileTrust (/app/node_modules/express/lib/utils.js:234:20) at Function.set (/app/node_modules/express/lib/application.js:389:34) at file:///app/src/app.js:28:5 ``` ### How can we reproduce the issue? I am not sure what is causing this error, so I'm not sure how it could be reproduced. ### Where are you hosting Actual? Docker ### What browsers are you seeing the problem on? Desktop App (Electron) ### Operating System Linux
GiteaMirror added the bug label 2026-02-28 20:01:26 -06:00
Author
Owner

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

I realized that IP was listed in my trusted proxies list like so:

172.16.0.0/16

However, this is a subnet and it doesn't seem to be bothered by any of the others I have in there. So I'm not sure why it's having an issue with this one?

@cordlord commented on GitHub (Apr 7, 2025): I realized that IP was listed in my trusted proxies list like so: ``` 172.16.0.0/16 ``` However, this is a subnet and it doesn't seem to be bothered by any of the others I have in there. So I'm not sure why it's having an issue with this one?
Author
Owner

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

I changed the value of the ACTUAL_TRUSTED_PROXIES EV to only be my main subnet, and it works now.

@cordlord commented on GitHub (Apr 7, 2025): I changed the value of the `ACTUAL_TRUSTED_PROXIES` EV to only be my main subnet, and it works now.
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/actual#2025