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

dep: bump phpipam version to latest v1.6.0 tag #83

Merged
merged 1 commit into from
Jan 9, 2024

Conversation

txj-xyz
Copy link
Contributor

@txj-xyz txj-xyz commented Jan 9, 2024

Changes are just directly to bump phpipam image version to latest checkout sha

https://github.com/phpipam/phpipam/releases/tag/v1.6.0

latest checkout: 0e9ec21c9d95f2bfcf91ffa93da4c4d470821421

@txj-xyz
Copy link
Contributor Author

txj-xyz commented Jan 9, 2024

@pierrecdn Thank you for the work!!

@pierrecdn
Copy link
Owner

Sure, let's try!

@pierrecdn pierrecdn merged commit a1a48b6 into pierrecdn:master Jan 9, 2024
@txj-xyz
Copy link
Contributor Author

txj-xyz commented Jan 9, 2024

Confirmed working on existing v1.5.2 installations.

No data loss over 15 instances.

@okand
Copy link

okand commented Jan 10, 2024

Upgrading to 1.6.0 made me unable to progress past the login screen. It will tell me if I entered correct credentials or not but either way I don't get to proceed into the site.

I use a reverse proxy so I suspect that is related to that change which seems to have been made in 1.6.0

  • Reverse-proxy users should review the new config.php $trust_x_forwarded_headers setting;

Adding IPAM_TRUST_X_FORWARDED=true as a variable didn't help, but I suspect it would if I were using their own docker image instead of this one.

Going back to 1.5.2 for now because I'm not that fussed about running the latest version anyway.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants