-
Notifications
You must be signed in to change notification settings - Fork 21
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
Unable to load WebUI #90
Comments
Would you mind providing your docker configuration you’re using? Be sure to remove any secrets you may have in your configuration. |
Not sure i can locate config in UI, as in unraid it is UI-based, but here is what i get when I do force update on docker image:
It is literally just TCP port, and 2 paths for /config and /assets that I pass from host. |
You don't seem to be binding/exposing a port.
-e 'TCP_PORT_3000'='3000'
This just sets an environment variable.
…On Fri, Jan 5, 2024 at 1:57 PM stomko11 ***@***.***> wrote:
Not sure i can locate config in UI, as in unraid it is UI-based, but here
is what i get when I do force update on docker image:
docker run
-d
--name='hammond'
--net='br0'
--ip='X.X.X.X'
-e TZ="Europe/Budapest"
-e HOST_OS="Unraid"
-e HOST_HOSTNAME="Tower"
-e HOST_CONTAINERNAME="hammond"
-e 'TCP_PORT_3000'='3000'
-e 'Community_Applications_Conversion'='true'
-l net.unraid.docker.managed=dockerman
-l net.unraid.docker.webui='http://[IP]:[PORT:3000]/'
-v '/mnt/user/appdata/hammond/config':'/config':'rw'
-v '/mnt/user/appdata/hammond/assets':'/assets':'rw' 'alfhou/hammond:latest'
It is literally just TCP port, and 2 paths for /config and /assets that I
pass from host.
Interestingly, i tried downloading hammond on one of other unraid servers
that I have around, that did not have hammond before. Same issue is
happening there, just blank screen regardless if i use network type host,
bridge, br0 or anything else (btw I use often br0 and assign IPs to my
dockers)
—
Reply to this email directly, view it on GitHub
<#90 (comment)>, or
unsubscribe
<https://github.com/notifications/unsubscribe-auth/ADRMX5ET24FS4JBWZLTHZQTYNBSKBAVCNFSM6AAAAABBO4JJVOVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQNZZGI2DOOBTGI>
.
You are receiving this because you commented.Message ID:
***@***.***>
--
Respectfully,
Alex Hess
|
I stand corrected. If your container is in fact using br0 as it's net there
should be no need for port mapping.
Based on the logs you gave from the hammond server it doesn't look like a
connection is being made.
If you can please open dev tools in your web browser, go to the network
tab, then in the address bar of the web browser navigate to your hammond
instance.
If you don't see any errors in the requests (i.e. 404), check the console
tab to see if any errors are shown there.
…On Fri, Jan 5, 2024 at 4:05 PM Mikey ***@***.***> wrote:
You don't seem to be binding/exposing a port.
-e 'TCP_PORT_3000'='3000'
This just sets an environment variable.
On Fri, Jan 5, 2024 at 1:57 PM stomko11 ***@***.***> wrote:
> Not sure i can locate config in UI, as in unraid it is UI-based, but here
> is what i get when I do force update on docker image:
>
> docker run
> -d
> --name='hammond'
> --net='br0'
> --ip='X.X.X.X'
> -e TZ="Europe/Budapest"
> -e HOST_OS="Unraid"
> -e HOST_HOSTNAME="Tower"
> -e HOST_CONTAINERNAME="hammond"
> -e 'TCP_PORT_3000'='3000'
> -e 'Community_Applications_Conversion'='true'
> -l net.unraid.docker.managed=dockerman
> -l net.unraid.docker.webui='http://[IP]:[PORT:3000]/'
> -v '/mnt/user/appdata/hammond/config':'/config':'rw'
> -v '/mnt/user/appdata/hammond/assets':'/assets':'rw' 'alfhou/hammond:latest'
>
> It is literally just TCP port, and 2 paths for /config and /assets that I
> pass from host.
> Interestingly, i tried downloading hammond on one of other unraid servers
> that I have around, that did not have hammond before. Same issue is
> happening there, just blank screen regardless if i use network type host,
> bridge, br0 or anything else (btw I use often br0 and assign IPs to my
> dockers)
>
> —
> Reply to this email directly, view it on GitHub
> <#90 (comment)>,
> or unsubscribe
> <https://github.com/notifications/unsubscribe-auth/ADRMX5ET24FS4JBWZLTHZQTYNBSKBAVCNFSM6AAAAABBO4JJVOVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQNZZGI2DOOBTGI>
> .
> You are receiving this because you commented.Message ID:
> ***@***.***>
>
--
Respectfully,
Alex Hess
--
Respectfully,
Alex Hess
|
I've seen Cannot find module ./da.json when the server doesn't have access
to the asset directory. I recently ran into this when I forgot to change
my volume paths in my docker-compose.yml.
Verify the container has access to /config and /assets directories. If
you're able to access a terminal within the container you'd be able to see
what's in there.
I don't use unraid so replicating this issue isn't currently possible for
me.
…On Fri, Jan 5, 2024 at 5:27 PM stomko11 ***@***.***> wrote:
OK so i have tested bridge again - in the bridge mode it is using `-p
'3000:3000/tcp' and it does not work anyway. I switched back to using br0
and assigned IP, and removed port completely - as with br0 it does not show
any container value. Buth in both cases it is not loading anything.
I do not agree that according to the logs from docker, it does not seem
like anything is connecting....
This is from docker logs, 192.168.88.154 is my clinet's IP:
GIN] 2024/01/06 - 01:21:23 | 200 | 2.116205ms | 192.168.88.154 | GET "/api/system/status"
[GIN] 2024/01/06 - 01:21:33 | 304 | 564.052µs | 192.168.88.154 | GET "/"
[GIN] 2024/01/06 - 01:21:33 | 200 | 236.149µs | 192.168.88.154 | GET "/api/system/status"
[GIN] 2024/01/06 - 01:21:43 | 304 | 1.422493ms | 192.168.88.154 | GET "/"
[GIN] 2024/01/06 - 01:21:43 | 200 | 1.452991ms | 192.168.88.154 | GET "/api/system/status"
In the console, I get following:
image.png (view on web)
<https://github.com/AlfHou/hammond/assets/88718231/26aabcf7-4d1d-4722-838d-01535d4edd86>
image.png (view on web)
<https://github.com/AlfHou/hammond/assets/88718231/ca23ae40-d725-40dc-a48f-e96d172efd46>
Not sure if these errors I see there are any helpful
—
Reply to this email directly, view it on GitHub
<#90 (comment)>, or
unsubscribe
<https://github.com/notifications/unsubscribe-auth/ADRMX5BXZ5TLTFMM5P5C3LLYNCLALAVCNFSM6AAAAABBO4JJVOVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQNZZGQ2TINRVGA>
.
You are receiving this because you commented.Message ID:
***@***.***>
--
Respectfully,
Alex Hess
|
I am seeing the exact same issue on a Debian host. Looks like the |
Yes, i can see both /assets and /conig from docker container, and I see the content that i should. btw - /assets is empty for me. But it is even with new install docker (and nothing works anyway, regardless if using :latest tag or alfhou/hammond:v0.0.21 I even tried I am clueless. I've got quite some experience with docker, unraid, and all that, and this is driving me nuts. Stopped working out of nowhere. I would understand if maybe my unraid instance got broken somehow. But it is not working on any other either. |
I will wait until it is merged |
Just to clarify for anyone else reading this thread. The /asset folder will remain empty unless you utilize the Quick Entry feature. da.json is transpiled into js chunks during the npm build process. Since it's currently malformed, this is causing issues but not failing during the build. |
I have started fresh and too are getting issues with WebUI not loading. My docker compose:
In browser console I get a:
|
PR #89 needs to be merged and then a new docker image built and published to docker hub. |
Yep - Also having the issue, aware of the PR. Just commenting so I get a notification when issue is closed |
Is there an estimate when this will be merged? Basically I am stuck now, reverting to older image does not work for me. |
I have this issue too:( |
Not sure if this works for others, but I was able to change back to the old
.21 release in my docker compose. At least until the PR is made, I am able
to access Hammond again.
version: '2.1'
services:
hammond:
image: alfhou/hammond:v0.0.21
|
For some reason, reverting to previous image does not work for me. |
If y'all don't mind building the docker image locally until @AlfHou is able to merge let me know. I'll provide the steps and help where I can. The changes aren't difficult and building is easy. |
Could you push a fixed image to docker hub please? |
I would if I could, but I don't have the permissions to do so. |
I think you should fork it to do so… |
@mada199122 it's only been a week since the PR was made. I think we can give Alf a bit more time. Again, if it's needed right now I can provide the steps to build it locally in the mean time. |
Yep of course, just in case it remains unsolved for a longer period |
Sorry didn't see this issue before now. I think I need to fix my notification settings. I'll get the PR merged as soon as I get to my computer today. Also, maybe I can look into letting @alienp4nda merge PRs and publish images as well. Hopefully the project will be a bit better maintained. Again, sorry for that |
The PR is merged, and a new image should be published. It seems to be working, but I'll leave the issue open until I get confirmation from more people. Again, sorry. I should've tested the previous release better. I'll strive to not let it happen again. |
I have tested now and it works for me. Thank you. |
1 similar comment
I have tested now and it works for me. Thank you. |
It works for me too!!! super thanks!!! |
Not sure what is going on - I am using docker image on my Unraid server. About 2 days ago, everything worked fine. Today, i was not able to load UI anymore. I thought OK - maybe something went wrong with the docker image. I redownloaded image, no luck. Tried resotirng backup of database from few days ago (multiple versions) - no luck either.
I decided to spin new docker image - but issue remains - when I open web page, it is just blank.
This is all I get in logs:
I did not have any other updates.
I also noticed that docker image has been updated yesterday, so I tried to use version before that -
alfhou/hammond:v0.0.21
but result is the same. i am clueless.Anyone has any idea?
The text was updated successfully, but these errors were encountered: