FrederikBaerentsen/BrickTracker
8
20
Fork 12
Code Issues 16 Pull Requests Actions Packages Projects 1 Releases 10 Wiki Activity

For some reason I cannot access the website (or worse: update BrickTracker) without a VPN... #164

New Issue
Open
opened 2026-06-20 14:55:47 +02:00 by riochicken · 5 comments
riochicken commented 2026-06-20 14:55:47 +02:00
Copy Link
Copy Source

Hi,

For some reason I cannot access the website (or worse: update BrickTracker) without a VPN...

When I use my phone with 5G or use a VPN on my laptop, it works, it seems that my ip address is blocked. Any thoughts?

Kind regards

Richard

Hi, For some reason I cannot access the website (or worse: update BrickTracker) without a VPN... When I use my phone with 5G or use a VPN on my laptop, it works, it seems that my ip address is blocked. Any thoughts? Kind regards Richard
FrederikBaerentsen commented 2026-06-20 14:58:06 +02:00
Owner
Copy Link
Copy Source

Which country are you accessing from? I am blocking some countries and IP ranges because of spam. If you could share the first couple of digits of your IP address, I’ll check it out.

Which country are you accessing from? I am blocking some countries and IP ranges because of spam. If you could share the first couple of digits of your IP address, I’ll check it out.
riochicken commented 2026-06-20 15:00:54 +02:00
Author
Copy Link
Copy Source

From the Netherlands.. 80.60.211 are the first couple of digits of my ip address (kpn the netherlands)

From the Netherlands.. 80.60.211 are the first couple of digits of my ip address (kpn the netherlands)
riochicken commented 2026-06-20 16:09:10 +02:00
Author
Copy Link
Copy Source

o minor detail: I was able to update using my mobile 5g connection the latest version was used but it still shows 1.4.0 Claude gave me the following information:

After upgrading to the :1.4.1 / :latest tag (image digest
sha256:77aa85d1aafaaa4409a2334b6dd49932f8f890776101f2fa57e6507e3cd92ce3),
the running container still reports version 1.4.0:

docker exec bricktracker cat /app/bricktracker/version.py
from typing import Final
__version__: Final[str] = '1.4.0'
__database_version__: Final[int] = 27

The 1.4.1 functionality (parts table column filters) is present and
working, so this looks like version.py just wasn't bumped when the
1.4.1 release was tagged/built. Minor cosmetic issue, but it makes it
hard to confirm which version is actually running via the admin UI or
container inspection.

o minor detail: I was able to update using my mobile 5g connection the latest version was used but it still shows 1.4.0 Claude gave me the following information: After upgrading to the `:1.4.1` / `:latest` tag (image digest sha256:77aa85d1aafaaa4409a2334b6dd49932f8f890776101f2fa57e6507e3cd92ce3), the running container still reports version 1.4.0: docker exec bricktracker cat /app/bricktracker/version.py from typing import Final __version__: Final[str] = '1.4.0' __database_version__: Final[int] = 27 The 1.4.1 functionality (parts table column filters) is present and working, so this looks like version.py just wasn't bumped when the 1.4.1 release was tagged/built. Minor cosmetic issue, but it makes it hard to confirm which version is actually running via the admin UI or container inspection.
riochicken commented 2026-06-20 16:11:11 +02:00
Author
Copy Link
Copy Source

and thank you for the quick reply!

and thank you for the quick reply!
FrederikBaerentsen commented 2026-06-20 19:45:40 +02:00
Owner
Copy Link
Copy Source

o minor detail: I was able to update using my mobile 5g connection the latest version was used but it still shows 1.4.0 Claude gave me the following information:

After upgrading to the :1.4.1 / :latest tag (image digest
sha256:77aa85d1aafaaa4409a2334b6dd49932f8f890776101f2fa57e6507e3cd92ce3),
the running container still reports version 1.4.0:

docker exec bricktracker cat /app/bricktracker/version.py
from typing import Final
__version__: Final[str] = '1.4.0'
__database_version__: Final[int] = 27

The 1.4.1 functionality (parts table column filters) is present and
working, so this looks like version.py just wasn't bumped when the
1.4.1 release was tagged/built. Minor cosmetic issue, but it makes it
hard to confirm which version is actually running via the admin UI or
container inspection.

Thank you! I’ll check it out.

About your IP, it isn’t banned and your country isn’t on my ban list. https://bricktracker.baerentsen.space/ Doesn’t have any country or IP restrictions, only Gitea does, so something might be wrong in your end if you can’t access that site. Sorry about that!

> o minor detail: I was able to update using my mobile 5g connection the latest version was used but it still shows 1.4.0 Claude gave me the following information: > > After upgrading to the `:1.4.1` / `:latest` tag (image digest > sha256:77aa85d1aafaaa4409a2334b6dd49932f8f890776101f2fa57e6507e3cd92ce3), > the running container still reports version 1.4.0: > > docker exec bricktracker cat /app/bricktracker/version.py > from typing import Final > __version__: Final[str] = '1.4.0' > __database_version__: Final[int] = 27 > > The 1.4.1 functionality (parts table column filters) is present and > working, so this looks like version.py just wasn't bumped when the > 1.4.1 release was tagged/built. Minor cosmetic issue, but it makes it > hard to confirm which version is actually running via the admin UI or > container inspection. Thank you! I’ll check it out. About your IP, it isn’t banned and your country isn’t on my ban list. https://bricktracker.baerentsen.space/ Doesn’t have any country or IP restrictions, only Gitea does, so something might be wrong in your end if you can’t access that site. Sorry about that!
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
Compat/Breaking
Breaking change that won't be backward compatible
 Kind/Bug
Something is not working
 Kind/Documentation
Documentation changes
 Kind/Enhancement
Improve existing functionality
 Kind/Feature
New functionality
 Kind/Security
This is security issue
 Kind/Testing
Issue or pull request related to testing
 Out of Scope
Request is out of scope
Priority
Critical
The priority is critical
Priority
High
The priority is high
Priority
Low
The priority is low
Priority
Medium
The priority is medium
Reviewed
Confirmed
Issue has been confirmed
Reviewed
Duplicate
This issue or pull request already exists
Reviewed
Invalid
Invalid issue
Reviewed
Won't Fix
This issue won't be fixed
Status
Abandoned
Somebody has started to work on this but abandoned work
Status
Blocked
Something is blocking this issue or pull request
Status
Need More Info
Feedback is required to reproduce issue or to continue work
Unraid
Unsupported/Can't help
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
FrederikBaerentsen
No Assignees
2 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: FrederikBaerentsen/BrickTracker#164
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?