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

Fail to upgrade from 4.12.7 to 4.15.8 #4139

Closed
jussara-ti opened this issue Jul 23, 2024 · 6 comments
Closed

Fail to upgrade from 4.12.7 to 4.15.8 #4139

jussara-ti opened this issue Jul 23, 2024 · 6 comments

Comments

@jussara-ti
Copy link

What version of GlobaLeaks are you using?

GlobaLeaks 4.12.7 under Debian11_x64 and Debian12_x64

What browser(s) are you seeing the problem on?

Chrome, Firefox

What operating system(s) are you seeing the problem on?

Linux

Describe the issue

Hello there,

After upgrade GlobaLeaks from version 4.12.7 to 4.15.8, I can't access the service anymore.

Is show the message "ERR_TOO_MANY_REDIRECTS" in the Chrome and Firefox browser.

I had test using Debian11 and 12 x64.

If I do a new install, the service work perfect.

Is there a way to work around this fail?

Proposed solution

No response

@evilaliv3
Copy link
Member

Hello!

Do you run any proxy in front of globaleaks?

@jussara-ti
Copy link
Author

No, there is no proxy in front of globaleaks.

@evilaliv3
Copy link
Member

Thank you.

Actually we are not aware of any bug on this matter.

Please feel free to share here or to me privately on community.globaleaks.org the address of the server and i may try to understand the reason.

@jussara-ti
Copy link
Author

jussara-ti commented Jul 24, 2024

Hello,
The server is in a private subnet.

How can I do sequential update on GlobaLeaks (4.13.x, 4.14.x)? to check if the problem still happening.
If I use apt, just the last release is available.

Thank's

@Hexdigest123
Copy link

Hello, you could potentially use the following official Docker image from GlobaLeaks:
https://hub.docker.com/r/globaleaks/globaleaks

As explained in the following issue: #4148 (comment)

@evilaliv3
Copy link
Member

Closing the ticket as stale.

@jussara-ti : plaase feel free to open it again if you need further assistance.

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

No branches or pull requests

3 participants