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

Puter Docker - No login via browser (intermittent wallpaper display) #350

Open
1 of 4 tasks
ianweatherburn opened this issue Apr 26, 2024 · 8 comments
Open
1 of 4 tasks

Comments

@ianweatherburn
Copy link

ianweatherburn commented Apr 26, 2024

Issue Description
puter is started via docker and is active at http://192.168.0.152:4100
CleanShot 2024-04-26 at 11 01 30
however fancy wallpaper intermittently appears in browser (mostly, not at all unless I clear cache - otherwise plain dark-blue background),
and more importantly, NO login appears at all so I cannot enter the default credentials provided to continue configuration.
Container shows as healthy, via the health-check so it is responding to the wget's

Steps to Reproduce
mount docker container via docker-compose.yml
[docker-compose.yml]
puter:
image: ghcr.io/heyputer/puter:latest
container_name: puter
restart: unless-stopped
pull_policy: always
environment:
- 'PUID=${PUID}'
- 'PGID={PGID}'
- 'TZ=${TZ}'
- 'CONFIG_PATH=/etc/puter'
ports:
- '${PUTER}:4100'
volumes:
- '${DATA}/puter/config:/etc/puter'
- '${DATA}/puter/data:/var/puter'
healthcheck:
test: wget --no-verbose --tries=1 --spider http://puter.localhost:4100/test || exit 1
interval: 30s
timeout: 3s
retries: 3
start_period: 30s

.env variables
PUTER=4100
PGID=1000
PUID=1000
TZ=Africa/Johannesburg
DATA=/home/iwadmin/docker/appdata

Expected & Actual Behavior
Login screen where default user credentials provided by the container can be captured and configuration/setup can continue/complete.

Addition Information or Screenshots (if applicable)
[config.json]
{
"config_name": "generated default config",
"env": "dev",
"nginx_mode": true,
"server_id": "ISENGARD",
"http_port": "4100",
"domain": "192.168.0.152",
"protocol": "http",
"contact_email": "[email protected]",
"services": {
"database": {
"engine": "sqlite",
"path": "puter-database.sqlite"
},
"thumbnails": {
"engine": "purejs"
},
"file-cache": {
"disk_limit": 16384,
"disk_max_size": 16384,
"precache_size": 16384,
"path": "./file-cache"
}
},
"cookie_name": "b302d23a-2cc1-48e8-b3c7-de3638c26e08",
"jwt_secret": "ce90b02f-38b5-430e-84e8-444430c7e08f",
"url_signature_secret": "6363a124-c639-48aa-886a-1a90063fadc9",
"": null
}

Deployment

  • Production (puter.com)
  • Development (npm run start)
  • Docker (via docker run)
  • Docker (via docker-compose)

Puter version (if accessible)

Click the profile button on the top-right, then "Settings". The version number will be printed at the bottom
Unable to access Settings as cannot login
ghcr.io/heyputer/puter:latest

** DEV CONSOLE Docker Output**
puter>
[INFO::morgan] method="GET" url="/test?" status=200 responseTime=5.226 trace_request="846499a1-5623-4bf4-831f-2b8c7edcd2e1" (8230.099s) GET /test? 200 5.226
[ Dev Console ]
*** WARNING ** WARNING ** WARNING ***
[alarm] bold-wallet-1101 (INVALID SYSTEM STATE...): failed to initialize services (1)
*** WARNING ** WARNING ** WARNING ***
*** SYSTEM IS IN AN INVALID STATE ***
┏━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━┓
┃ ┃
┃ Puter is now live at: �]8;;http://192.168.0.152:4100�\http://192.168.0.152:4100�]8;;�\
┃ Type web:dismiss to dismiss this message ┃
┃ ┃
┗━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━┛
┏━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━┓
┃ Your default user has been created! ┃
┃ username: default_user ┃
┃ password: 33c7b6a7 ┃
┃ (change the password to remove this message) ┃
┗━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━┛

@ianweatherburn
Copy link
Author

CleanShot 2024-04-29 at 11 17 25
Further console info

@AtkinsSJ
Copy link
Collaborator

This looks like the same as #230, you could try this solution from there:

So far we've added a config option to remove the requirement of a api. subdomain:

    "experimental_no_subdomain": true,

Originally posted by @KernelDeimos in #230 (comment)

@ianweatherburn
Copy link
Author

ianweatherburn commented Apr 29, 2024

This looks like the same as #230, you could try this solution from there:

So far we've added a config option to remove the requirement of a api. subdomain:

    "experimental_no_subdomain": true,

Originally posted by @KernelDeimos in #230 (comment)

Thank you. This has fixed the login issue.
However, no App Centre, Dev Center, no Browser, Terminal doesn't work.

@AtkinsSJ
Copy link
Collaborator

AtkinsSJ commented May 1, 2024

Thank you. This has fixed the login issue. However, no App Centre, Dev Center, no Browser, Terminal doesn't work.

App Centre, Dev Center, and Browser being missing is expected, we don't include those now, but we will do later.

Can you explain what issues you're having with the Terminal?

@ianweatherburn
Copy link
Author

Thanks for the clarification. Terminal fails to start. Window opens, cursor, no prompt. No error message in docker logs.
CleanShot 2024-05-02 at 09 24 43

@AtkinsSJ
Copy link
Collaborator

AtkinsSJ commented May 2, 2024

OK. First, after opening Terminal, can you have a look at the Task Manager in Puter? It's in this menu and should have an entry for "phoenix" underneath the "terminal" one, like so:
image

Second, if you can look at the browser console again, there should be some kind of clue there.

And finally, what version of Puter is it running? It'll be on the "About" tab of the Settings app. We did recently have issues with the terminal and I don't know how Docker updates things, but it might be running an older version somehow.

@ianweatherburn
Copy link
Author

  1. Task Manager is in line with your screenshot.
    CleanShot 2024-05-02 at 15 31 18

  2. Browser Javascript Console after launching Terminal
    Arc Browser v1.40.1
    CleanShot 2024-05-02 at 15 34 52
    Safari Browser v17.14.1
    CleanShot 2024-05-02 at 15 38 04

  3. Puter Docker Version :latest
    Version: 2.1.0 • Server: ISENGARD • Deployed: 02/05/2024, 15:31:56

@AtkinsSJ
Copy link
Collaborator

AtkinsSJ commented May 6, 2024

Thanks. I'm a bit confused. The errors that contextlink and main_shell are not defined mean it's probably an issue with installing nested dependencies - but that should have been fixed before 2.1.0.

I'm going to spend some time today setting up Docker to see if I can reproduce this.

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

No branches or pull requests

2 participants