Open krillin666 opened 2 months ago
Maybe my problem is related. Plant-It is running and i can connect to plantit.MYDOMAIN.com/auth
Now i can login or create an user (first start). When i want to create my user, it shows: "ERROR" with no information in the logs.
I am using docker with traefik config as here: https://github.com/MDeLuise/plant-it/issues/144
Hi! Could you please share the docker-compose log?
Hi! Could you please share the docker-compose log?
Just edited my post with all my configs. Thank you!
Maybe my problem is related. Plant-It is running and i can connect to plantit.MYDOMAIN.com/auth Now i can login or create an user (first start). When i want to create my user, it shows: "ERROR" with no information in the logs.
I am using docker with traefik config as here: #144
I'm having this issue as well. New install, http host with an Nginx Proxy Manager https connection.
@krillin666 - I have narrowed our issue down to using an external reverse proxy. Changing my API_URL from https://my.domain.com/api to http://192.168.1.50:8080/api resolved the error and I was able to create a user and log in. I had hoped that after I created the user I could switch back to my FQDN but no dice.
@krillin666 - I have narrowed our issue down to using an external reverse proxy. Changing my API_URL from https://my.domain.com/api to http://192.168.1.50:8080/api resolved the error and I was able to create a user and log in. I had hoped that after I created the user I could switch back to my FQDN but no dice.
Thanks for sharing your findings @ishcabittle ! @MDeLuise congratulations with the new release ! Do you know if we now set the backend to a reverse proxy address these problems will still be present ? I can test it later today, @ishcabittle did you tried it already ?
Hi there!
@MDeLuise congratulations with the new release ! Do you know if we now set the backend to a reverse proxy address these problems will still be present ?
Thank you for the congratulations! While it's not entirely clear why these issues are occurring, I recommend giving the new release a try. With the frontend of the app being fully rewritten (transitioning from TypeScript to Flutter), different frameworks may handle HTTP requests differently, which could potentially resolve the problems you've encountered.
Please keep in mind that there have been some changes to the deployment process in this release, as outlined in the release notes.
Additionally, it's worth noting that the Traefik deployment in the documentation may need some updates.
Let me know if the 0.5.0
version of the project addresses these issues for you.
If not, we'll dive deeper into finding a solution
@krillin666 - I have narrowed our issue down to using an external reverse proxy. Changing my API_URL from https://my.domain.com/api to http://192.168.1.50:8080/api resolved the error and I was able to create a user and log in. I had hoped that after I created the user I could switch back to my FQDN but no dice.
Thanks for sharing your findings @ishcabittle ! @MDeLuise congratulations with the new release ! Do you know if we now set the backend to a reverse proxy address these problems will still be present ? I can test it later today, @ishcabittle did you tried it already ?
I did upgrade to the new release, unfortunately I am still receiving the network error. Because it works perfectly when pointing to the internal IP address, I'm fine with it for now.
@krillin666 - I have narrowed our issue down to using an external reverse proxy. Changing my API_URL from my.domain.com/api to http://192.168.1.50:8080/api resolved the error and I was able to create a user and log in. I had hoped that after I created the user I could switch back to my FQDN but no dice.
Thanks for sharing your findings @ishcabittle ! @MDeLuise congratulations with the new release ! Do you know if we now set the backend to a reverse proxy address these problems will still be present ? I can test it later today, @ishcabittle did you tried it already ?
I did upgrade to the new release, unfortunately I am still receiving the network error. Because it works perfectly when pointing to the internal IP address, I'm fine with it for now.
I'm trying to deploy the new version from start, but I'm getting cannot connect to the server error
. And when I try to access the db it shows Bad Request This combination of host and port requires TLS.
Hi everyone, I wanted to share an update regarding Traefik. I've successfully set up a functional local environment, which might be useful for those of you using Traefik (or are using other proxy maybe). I'll be sure to incorporate this into the official documentation to highlight its utility.
Here's the configuration for the working deployment:
version: '3'
services:
reverse-proxy:
image: traefik:v3.0
command: --api.insecure=true --providers.docker
ports:
- "80:80"
- "8080:8080"
volumes:
- /var/run/docker.sock:/var/run/docker.sock
server:
image: msdeluise/plant-it-server:0.5.1-beta
env_file: server.env
depends_on:
- db
- cache
restart: unless-stopped
labels:
- "traefik.enable=true"
- "traefik.http.routers.app.rule=Host(`plant-it.docker.localhost`)"
- "traefik.http.routers.app.service=server"
- "traefik.http.routers.app.entrypoints=http"
- "traefik.http.services.server.loadbalancer.server.port=3000"
- "traefik.http.routers.api.rule=Host(`plant-it-api.docker.localhost`)"
- "traefik.http.routers.api.service=server-api"
- "traefik.http.routers.api.entrypoints=http"
- "traefik.http.services.server-api.loadbalancer.server.port=8080"
db:
image: mysql:8.0
restart: always
env_file: server.env
volumes:
- "./db:/var/lib/mysql"
labels:
- "traefik.enable=false"
cache:
image: redis:7.2.1
restart: always
labels:
- "traefik.enable=false"
In this example you can visit http://plant-it.docker.localhost
for accessing the app, and http://plant-it-api.docker.localhost/api/swagger-ui/index.html
for accessing the Swagger UI.
Use http://plant-it-api.docker.localhost
as server URL when request in the app setup.
Avoid duplicated bug reports
Description
After creating a user in the platform it automatically logins as this user. However, if attempting to login using these credentials in another device, browser, or in the same browser (after whipping data) it gives a bad credentials error.
I've tried creating multiple users and this error happens always. In the backend logs I see something like
Temporary password for user MyUsername not found
. I don't have access to the logs now, but I can post them later.Thank you so much for your work!
Expected behaviour
No response
Steps to reproduce
No response
Local environment
Running on a RPI 4 with debian bookworm 64bits. Latest docker version with reverse proxy using nginx. I'll post my config later!
docker-compose:
Backend:
Frontend:
Logs:
Additional info
No response