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

Bug? UI in Dockerimage not able to load all resources #829

Closed
VfBfoerst opened this issue Dec 19, 2024 · 6 comments
Closed

Bug? UI in Dockerimage not able to load all resources #829

VfBfoerst opened this issue Dec 19, 2024 · 6 comments
Labels
bug Something isn't working

Comments

@VfBfoerst
Copy link

What Happened?

Hi :)
I wanted to try the docker image (I tried version 1.8.5, 1.8.4, 1.8.3), but the ui does not show up as expected. It fails to load the additional ressources.
UI looks at the moment like that:
image

Console:
image

As copy-paste:

Failed to load resource: the server responded with a status of 404 (Not Found)
tabs.css:1 
        Failed to load resource: the server responded with a status of 404 (Not Found)
buttons.css:1 
        Failed to load resource: the server responded with a status of 404 (Not Found)
interative-code.css:1 
        Failed to load resource: the server responded with a status of 404 (Not Found)
modal.css:1 
        Failed to load resource: the server responded with a status of 404 (Not Found)
styles/style.css:1 
        Failed to load resource: the server responded with a status of 404 (Not Found)
logs.css:1 
        Failed to load resource: the server responded with a status of 404 (Not Found)
snippets.js:1 
        Failed to load resource: the server responded with a status of 404 (Not Found)
main.js:1 
        Failed to load resource: the server responded with a status of 404 (Not Found)
hotjar-3502316.js?sv=7:3  For security reasons, Hotjar only works over HTTPS. Learn more: https://help.hotjar.com/hc/en-us/articles/115011624047
window.hjBootstrap @ hotjar-3502316.js?sv=7:3
wtp.js:17 handleResponse
wtp.js:20 file_name is 
wtp.js:22 path is chrome-extension://dlmffppdphadfmicefckcdnpaokpdmbm/
wtp.js:24 type of tmext is undefined
wtp.js:25 type of message is undefined
public:1  Error handling response: TypeError: Cannot read properties of undefined (reading 'databc')
    at handleResponse (chrome-extension://dlmffppdphadfmicefckcdnpaokpdmbm/wtp.js:26:46)
    at chrome-extension://dlmffppdphadfmicefckcdnpaokpdmbm/wtp.js:83:5
public:1  Unchecked runtime.lastError: A listener indicated an asynchronous response by returning true, but the message channel closed before a response was received
[NEU] Erläutern von Konsolenfehlern mithilfe von Copilot in Edge: Klicken Sie auf
         , um einen Fehler zu erklären.
        Weitere Informationen
        Nicht mehr anzeigen
Microsoft Edge is moving towards a new experience that allows users to choose to browse without third-party cookies.
tabs.css:1 
        Failed to load resource: the server responded with a status of 404 (Not Found)
header.css:1 
        Failed to load resource: the server responded with a status of 404 (Not Found)
interative-code.css:1 
        Failed to load resource: the server responded with a status of 404 (Not Found)
buttons.css:1 
        Failed to load resource: the server responded with a status of 404 (Not Found)
logs.css:1 
        Failed to load resource: the server responded with a status of 404 (Not Found)
modal.css:1       
        Failed to load resource: the server responded with a status of 404 (Not Found)
style.css:1 
        Failed to load resource: the server responded with a status of 404 (Not Found)

I tried edge browser as well as firefox.

What Should Have Happened?

UI should be able to load all of its resources succesfully.

Relevant Code Snippet

Deployment via:

docker run --rm  -p 8787:8787 portkeyai/gateway:1.8.5

Your Twitter/LinkedIn

No response

@VfBfoerst VfBfoerst added the bug Something isn't working label Dec 19, 2024
@VisargD
Copy link
Collaborator

VisargD commented Dec 19, 2024

Hey, we are looking into this issue. Thanks for reporting!

@roh26it roh26it removed the triage label Dec 19, 2024
@roh26it
Copy link
Collaborator

roh26it commented Dec 19, 2024

@VfBfoerst Can you try this url once - "http://localhost:8787/public/"

The last slash might be what's causing the issue. Will fix this in the next release.

@VfBfoerst
Copy link
Author

@roh26it thank you! Yeah i will try it tomorrow.

@VfBfoerst
Copy link
Author

Can confirm its because of the slash. Works with the slash at the end.

@VisargD
Copy link
Collaborator

VisargD commented Dec 20, 2024

We have also pushed a fix for this in #832. It will be a part of next release happening today

@VisargD
Copy link
Collaborator

VisargD commented Dec 23, 2024

This went live in v1.8.6.

@VisargD VisargD closed this as completed Dec 23, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

3 participants