-
Notifications
You must be signed in to change notification settings - Fork 419
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
Geoserver trouble with admin password #509
Comments
You should be building the image using
|
Thank you for your suggestion. The container eventually started (I think I was just being impatient with Geoserver). Now, I'm having issues with logging in.
|
If I run |
are you not able to login with the password ?, if you pass an env variable that should not be visible in the logs |
I still can't log in. Would it help if I posted the log output here? |
Yes, share the logs and possibly a gif showing the problem. |
Here is the log file. You can see at the bottom, my failed login attempts.
|
I've tried everything I can think of. Is there a reason the |
Can you please share the command and the env file with some random values for me to test this |
Thank you for your offer. The Geoserver container is part of a larger configuration of containers such as Apache for a web server, your postgis for data storage and analysis, a postgres backend for Geowebcache management, a python container for an API, and a python container for load testing, all strung together in a docker-compose file. I'm not sure I could strip it down for you, but I will try. In the meantime, could you help me understand how the I see in this section on upgrading image to use a specific version that I should have I also see in this section on changing Geoserver password and username that:
But that to set a new password I:
I look at the logs after each attempt, and I am fairly certain that I have never seen any of the echo statements print out from Also, as I mentioned above, I am upgrading from a previous version (2.17.2) and have an existing data directory. I obviously want this to persist whilst I upgrade the Geoserver container version. But could there be some configuration in there that is causing this chaos? My situation right now is that no password seems to work for me. So, how do I set a |
As a last restore please try to use the env variable |
Thanks. I will give this a try. |
The demo is helpful to see. I have never doubted that a fresh pull and build works as expected. Unfortunately, I am trying to do a version upgrade on an existing instance, which is a little different... |
Sorry for the confusion, @kristofj-umd is another account that I have. |
@rumski20, @kristofj-umd If there is, the
try stopping the geoserver instance, delete the file, and restarting it with the ADMIN environment variables. |
Thanks for the suggestion, @ggsggs. I tried it but I think I'm taking some steps backwards here. Now I can't even get the default page to load to attempt a login. 😞 I had tried building the image locally and using that. I think I'll go back to pulling the image from docker hub. |
@rumski20 Maybe we could have a quick meeting to resolve this as I can give you pointers and if you need any other support after we could assist at https://kartoza.com/product/support |
@NyakudyaA , thanks for your offer. I would be happy to meet with you about this. Let me know how we could make that happen. I turned the Geoserver logging up to verbose and, accordingly, it spits out a much bigger log file while it starts up. I wonder if it may be of any use. |
I tried running the health check curl command:
locally on the container and it returned 401 authentication errors. Now I am trying to build and run the container using this suggestion. It is taking a while to debug this because I have so many existing layers, styles, and geowebcache data (over 500 layers). |
The site still won't show up on the webserver that should be serving it (eg. http://some-domain/geoserver/web) but if I run this command:
It seems to connect. Here's the output:
Note that I couldn't use the user and password set in the env variables as in this command:
|
@rumski20 send me an email |
Sure. What's your e-mail? I'm at rumski20@msn.com if you want to contact me. |
Okay, some progress, but I'm still not there. I fixed the issue with the site not coming up at all. For some reason the Apache web proxy container needed its config slightly tweaked. So now I can try logging in again. I created a container with
and I was able to login. However, the link to change the admin and master passwords from the web interface didn't work. Possibly related to this issue: https://stackoverflow.com/questions/66526411/geoserver-advice-please-http-status-400-bad-request
I changed the I found this in the logs after that failed attempt if it helps:
|
I should also add that I see this message on one of the first lines of the log file
Also, I just tried logging in again and |
If you use |
As in a fresh install stand alone container? |
Yes, stand-alone container |
Yes, I can confirm this works. I essentially repeated what you did here:
|
I've tried everything I can think of to change the password, but it still seems stuck at Here is my setup:
|
+1 I'm facing the same issue: No admin password is generated and |
@rumski20 Could you please change the title to state there are issues with the admin password? I can help others that are facing the same problem to know that it's a known issue. |
There seem to be multiple issues with v2.22.2. Some of these have been resolved in the However, even with that build, it's still not possible to log in with a supplied or generated password. It looks like there is a problem with the generated
|
@jasny Does this mean you were able to log in to the web interface using the |
No, I literally need to use "GEOSERVER_ADMIN_USER" as username. I didn't supply a password and use the randomly generated one. But it should take the value of the env var afaics. Note that this is on the |
😲 Yeah, that don't seem like how it's supposed to work. |
Anyhow, I finally got an instance up and running that I was able to login to with the @NyakudyaA , @ggsggs thanks for all your help and support. I can't be sure that it's entirely reproducible (given that this container is part of a whole docker-compose setup with multiple moving parts), but for posterity here (after much trial and error) is what seems to be the correct workflow: problem: couldn't login using the solution:
If all goes as planned, you should be able to login with the password that is actually specified for |
@jasny @rumski20 I have just tried this and all is working properly on the latest develop. Here is what I have done
Use the password specified in the startup logs to log in on the browser.
Log in using Can you try the above and confirm if it gives errors? If we can confirm this, I can update the images. |
@NyakudyaA 👍 Yes, I can confirm that everything works when using the image build from the To solve the username issue in my environment, I needed to delete the |
@jasny Please check he 2.23.0 images released. They have the password fixes |
So... for the record, we have an instance that is doing the same thing after upgrading to 2.18.7 -- "admin" user no longer works with our admin password that gets included as an environment variable. But 🤷♂️ |
I keep getting application error when i mount a volume, any help please? |
What is the bug or the crash?
I am attempting to re-build Geoserver using this docker recipe. Previously I had been using the tag
2.17.2
. When I change the tag to the latest version (2.22.2
) and rebuild this containerIt doesn't seem to start up properly.
docker-compose ps
reports it as up, but the Apache reverse proxy I haven't in front returns a 503 error. And hitting it locally from within the containerreturns
The container logs seem to be cut-short as well:
Any advice you have for debugging this or getting to the root cause would be much appreciated.
Thank you for this docker recipe.
Steps to reproduce the issue
Build container using latest version within docker-compose arrangement.
Versions
Latest (2.22.2)
Additional context
No response
The text was updated successfully, but these errors were encountered: