Login issues #27
Comments
|
if you don't ship your own certificates, the connexion on https is insecure but the connexion on http works without those certificates. You can login with The most basic way to run the emoncms container is : There is more help on the discussion part of the repo : And also on the specific documentation site : I also mostly don't run the docker image with https but with http I don't use portainer but simply docker and docker compose anyway things should work straigthforward with portainer. Which tag do you use ? latest ? PS : If you want more detailed help, please give more context, I dont know how portainer works.... PS2 : I've understood you dont want to run https, but there is some info here https://github.com/Open-Building-Management/containers/tree/main/emoncms/alpine_persistent#adding-ssl-and-https-for-secure-operation |
|
Edit : things work also fine with portainer
small test with the latest tag the log should be something like that then browsing to http://127.0.0.1:8999 gives : |
|
Many thanks for your prompt reply. I was having issue with the machine/browser that I was testing on, it worked fine on http port 8081 on another machine. |
|
I am having issues with login username/password though. I register making a new name and password, then try to use it, but the password fails, and I no longer have the opportunity to re-register, how do I fix this? |
|
This is a single user installation of emoncms. So if you forget the password, you have to delete your container and recreate a new one. |
|
Deleting container did not work. Since I have a named volume, I guess I have to delete that as well ..? |
|
So I deleted the container, and the volume, started again, and now I can register again, but when I try to login with that username/password I set, it does not work, and the register option is gone again ... what gives ....? I am using the "latest" image. |
|
I guess you speak of a named volume for the data ? It is more designed to be used with a bind, but indeed it should work with a volume. So if you forgot the password you entered, and if you delete the data bind, you will be able to restart the registration from the beginning. As far as mysql and mqtt settings, they are defined as env vars. mqtt details can be changed when you want, mysql credits only at the first container run....of course they dont have to match with the emoncms user and password https://emoncms-docker.github.io/setup/ When you register the first time, you are automatically logged in. What have you done then ? Did you restore a backup ? If yes, then you restored the user name and password associated to the backup and when you login the next time you have to use this username and password associated to the backup..... If you want help, you need to explain what you are trying to achieve. Give screenshots, show log extracts.... |
|
Also reported here : emoncms/emoncms#1915 |
alexandrecuer
added
cannot reproduce - need details
and removed
bug
Hi, I have this sort of running in portainer. However, there are a couple of issues:
The webpage does not come up correct on http port 8081, it just shows the login page, but only with the door at top right, nothing else. Clicking the door does nothing.
If I login via https, I can get in and enter my account details, however the page is insecure. I take it the certificates have not been set up.
I don't need https for my application, so help getting login via http would be good.
The text was updated successfully, but these errors were encountered: