[BUG] 404 on GitLab pages with Base_URL

[cchaudier]

Environment

Cloud Service (Static)

Version

1.9.3

Describe the problem

Hello,

I wanted to test Dashy to create a dashboard for our online tools at @LydraFr, as we have many of them.

I'm more and more attracted by static sites and Jamstack for simplicity of hosting and ecology constraints.
So I wanted to use the static site with Froggit Pages, a French equivalent of GitLab Pages.
I followed the doc here : https://dashy.to/docs/deployment#hosting-with-cdn

But I have a problem because the site displays a 404 page.
But when I click on Back Home the site is displayed but the url is not correct anymore.

I also tried on the GitLab Pages but I have the same problem.

I use the Docker image to build the app in GitLab-CI.
I have declared BASE_URL to put the path of my site.
But in the console log I see:
⚠️ Warning ⚠️ Route not found: '/poc/dashy/'

I also see a CORS error that seems to be the origin of my 404 :
404:1 Access to XMLHttpRequest at 'https://app-directory.s3.amazonaws.com/hootlet/launched-app-directory-apps.json' from origin 'https://lydra.gitlab.io' has been blocked by CORS policy: No 'Access-Control-Allow-Origin' header is present on the requested resource.

• My GitLab repository : https://gitlab.com/lydra/poc/dashy
• The generated files : https://gitlab.com/lydra/poc/dashy/-/jobs/1851220666/artifacts/browse/public/
• The generated site: https://lydra.gitlab.io/poc/dashy/

I don't know what to do anymore.
PS: I have no problem locally with my docker-compose.

Additional info

No response

Please tick the boxes

• You are using a supported version of Dashy (check the first two digits of the version number)
• You've checked that this issue hasn't already been raised
• You've checked the docs and troubleshooting guide
• You agree to the code of conduct

Deployment | Dashy

Welcome to Dashy, so glad you're here :) Deployment is super easy, and there are several methods available depending on what type of system you're using. If you're self-hosting, then deploying with Docker (or similar container engine) is the recommended approach.

Lydra / poc / Dashy

GitLab.com

public · Artifacts · pages (#1851220666) · Jobs · Lydra / poc / Dashy

GitLab.com

Dashy

[Lissy93]

Hiya @cchaudier - Thanks for your issue. Could you try setting the routing mode to hash, from what you describe I think this could be the issue, but I will look into it further when I get home this evening :) Just add this into your appConfig:

appConfig:
  routingMode: hash
  ...

P.s Thanks for the really clear issue, and relevant resources, it makes debugging so much easier :)

I am a bit confused about that 401 CORS error though, as it doesn't seem to link to any of Dashy's files, and I don't see it on my machine. Could this be a previous app that's cached, and if so do you see different results when in Incognito/ after clearing the cache?

I think it's most likely Vue router, so try hash mode, and we can go from there :)

[cchaudier]

Thanks @Lissy93 for the suggestion.

The routingMode: hash fixe the problem, I don't have 404 anymore.

I will make a sample repository on GitLab to propose a .gitlab-ci.yml sample file and maybe a video on the YouTube channel.

If you are interested I can make a pull request for the Dashy documentation.
I don't know if on Github pages the problem would be the same.
The CORS error is still there, even in private browsing, but does not crash the static site to work.

[Lissy93]

I'm glad that's working now :)
That would be awesome if you could! Thank you :)

I wonder what is causing that CORS error, the URL in the error isn't actually one included anywhere in Dashy, so could it possibly be either something to do with an extension you have installed, or maybe something GitLab pages in injecting? Do you have an old Hootsuite extension installed? That would be my best guess from the URL in the error message. It does seem worrying though, so probably worth looking into

[Lissy93]

Closing ticket as main issue is solved.

I'll update the docs with the relevant info this weekend.

And after looking into the Cors error further, I belive its due to a browser extension, likley something related to Hootsuit (but do correct me if you think I'm wrong).

Feel free to reach out if you need anything else :)