frappe/helpdesk

assets/helpdesk/desk/assets/index-afe95341.js net::ERR_ABORTED 404 (Not Found)

Closed this issue · 8 comments

Information about bug

Im Installing helpdesk from main branch into my self-hosted VM in GCP of my production frappe installation via frappe_docker. but when I open my frontpage of the helpesk I got asset 404 not found

Version

erpnext 15.40.0
frappe 15.46.0
helpdesk v1.0.0

Installation method

docker

Relevant log output / Stack trace / Full Error Message.

GET https://myapp.com/assets/helpdesk/desk/assets/index-afe95341.js net::ERR_ABORTED 404 (Not Found)
helpdesk:203 
       GET https://myapp.com/assets/helpdesk/desk/assets/index-fc83c5d5.css net::ERR_ABORTED 404 (Not Found)
helpdesk:204       
       GET https://myapp.com/assets/helpdesk/desk/registerSW.js net::ERR_ABORTED 404 (Not Found)
manifest.webmanifest:1 
       GET https://myapp.com/assets/helpdesk/desk/manifest.webmanifest 404 (Not Found)

I have done bench build --app helpdesk but problem still exist

I got exact same problem using manual installation (not docker)

Same problem here but on my custom app on frappe cloud. Building on my local environment works fine. I've got the 404 deploying on Frappecloud. I guess is something related to permission.

Are you guys still facing the issue?
@SoledeSA
@bilalbayasut
@bb-mcg
??

Yes, the problem is still up in my custom app.
I've opened a ticket with the support team (https://support.frappe.io/helpdesk/)
Ticket ID: 25644
Thanks!

Im forced to not use docker then it is working

I have added docker image in the helpdesk, you will be able to install it with docker, with ease.
Let me know if you face some issues

Closing due to inactivity

@RitvikSardana sorry for commenting after this was closed, but when I try to pull ghcr.io/frappe/helpdesk, I get the following error:
Error response from daemon: manifest unknown

Any idea why? This happens when I try to install via the python script and when I try to manually pull the docker image. (Btw I cannot install helpdesk at all currently. It seems to fail specifically while pulling the backend.)

Edit: now it's queue-short, so it doesn't seem to be specific to one specific container, but more so the entire image.