Skip to content
This repository has been archived by the owner on Apr 17, 2023. It is now read-only.

blank page for namespace #2315

Open
Ajeeshb opened this issue Jul 17, 2020 · 5 comments
Open

blank page for namespace #2315

Ajeeshb opened this issue Jul 17, 2020 · 5 comments
Labels

Comments

@Ajeeshb
Copy link

Ajeeshb commented Jul 17, 2020

I am getting a blank page while clicking the namespace section. But the same time I can see the namespace if i am accessing the exact URL http://172.16.1.149:3000/namespaces/5

I can see the following error in the console of the web browser.

Uncaught TypeError: Cannot read property '__vue__' of undefined
    at HTMLDocument.<anonymous> (bootstrap.js:16)
    at c (jquery.js:3534)
    at l (jquery.js:3602)



@Ajeeshb
Copy link
Author

Ajeeshb commented Jul 17, 2020

Hi Team,
I have reinstalled everything and it started working. No idea what caused it.

@stampeder
Copy link

Do you have Portus working? I tried the official image and it doesn't work. What are you using?
Thanks.
Glenn.

@Ajeeshb
Copy link
Author

Ajeeshb commented Jul 20, 2020

I have configured Portus with my AD login integration. Actually I have configured with an insecure local docker registry.

I too have some issues with running the docker container. After checking its the problem with the config.yml. I have changed some settings on that file. But right now i could not see the docker image listing in portus web UI. But I can pull/push images from my docker registry and user management from portus.

@jhrcz
Copy link

jhrcz commented Oct 14, 2020

hi after long love without /namespaces page i found, that after upgrade from some older version and with trying to still have working ldap integration (and moved from openldap to AD), all users in db have namespace_id set to NULL. comparing it to local test install of portus and manualy fixing namespace_id to coresponding id from namespaces fixed the blank /namespace page.

@stale
Copy link

stale bot commented Jan 9, 2022

Thanks for all your contributions!
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs.

@stale stale bot added the stale label Jan 9, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Projects
None yet
Development

No branches or pull requests

3 participants