Good morning,
I encounter a 404 error on the pages of the collection elements. I can modify them in the CMS (and preview them), but when I consult them via the published link, I get a 404 error indicating “The requested resource cannot be found”.
Here is the link to visualize the error:https://p.whc.ca/file/A7bbLhoCV0xqE63K/0sbbqQgEg0Pd5FRR/Error%20404.mov?dl=1
Thank you very much,
Hi Mehdi,
Thanks for the video — since you’re using cPanel, this looks like a publishing/server issue, not just a collection setup problem.
The error during publish suggests the site wasn’t fully deployed, which can easily lead to 404 errors on collection pages.
I also think this might be the issue. Please try to make a small change, save and re-publish. Maybe you have to try this a few times. If that does not help, you need to either contact cPanel directly or your provider needs to contact cPanel. They need to check on the publishing process in that case.
Keep us updated please!
This solution worked for me in the past. I sent my host an email, and they confirmed that there was a glitch between them and cPanel. The bug was fixed quickly.
I hope this works.
.. and then update us here as well 
because we are curious 
Hello everyone,
We identified the cause of the publishing issue.
After further investigation, it turns out the failure was not caused by the content itself, but by a technical server limitation: the generated file path or URL (in another collection) was too long for the system to handle.
More specifically, during publication, the server attempted to create a directory with an extremely long name, which triggered a “File name too long” error.
In short, the issue is caused by an excessively long title being converted into a file path or URL.
Recommended solution:
shorten the file name, slug, or publication URL, and then try the publishing process again.
I hope this could help for any future inconvenients.
Thank you!