When I try to access activepieces I have run in docker I get a blank page instead of the activepieces welcome page. The reason I’m trying this because I want to be able to access activepieces from other machines in my local network.
So: http:// localhost:8080 or http:// 127.0.0.1:8080 work (I can logon), but
http://my.machine.internal or http://10.31.29.246:8080 doesn’t.
(I have added my.machine.internal to my host file).
I have tried with the default docker approach as outlined on: Docker - Activepieces
Beware!: the spaces after http:// are deliberate. Otherwise I could not post this.
With commandline:
docker run -d -p 8080:80 -v ~/.activepieces:/root/.activepieces -e AP_REDIS_TYPE=MEMORY -e AP_DB_TYPE=PGLITE -e AP_FRONTEND_URL=”http:// localhost:8080” activepieces/activepieces:latest
Obviously replacing the AP_FRONTEND_URL with the various options like host name or local IP number.
Then I tried the docker approach as described on: Docker Compose - Activepieces
I used the one from tag 79.4 since newer ones don’t seem to work for me.
I replaced AP_FRONTEND_URL in the .env file with the various url’s to see what works. Answer: nothing. I keep getting an blank page.
Then I decided to try another approach to see whether my machine(s) or docker were the problem. I ran this little “hello world” web server test: crccheck/hello-world:latest
I tried this on port 80 and 8080. On both I could reach the test via my.machine.internal and 10.31.29.246
So I can rule out ports being blocked.
I’ve been banging my head against the wall with this. I hope someone can help.
I have developed some code for the project and I want to test it. But this is blocking me.
I also supplied the screen shots of the trace and error message I see when I get the blank page.
Regards,
