CMS - Media Upload - FILETYPE NOT ALLOWED Error

Hi Xibo Team,

Our team is having with uploading media/files in our CMS.

We did not do or change anything in the settings in both CMS and server sides.
We just tried to upload new medias/files for our layouts and all files uploaded suddenly displays an error saying “Filetype not allowed”

Please see the screenshot for reference:

Troubleshooting we’ve done so far:

  • restart CMS server
  • delete old files/medias to clear some storage
  • check settings / display settings

All tried resolutions did not resolve the issue so far,

Advise from your team will be much appreciated,

Thank you very much Xibo Team as always,

What’s the CMS version and how is it installed please? (docker or manual installation)

Could navigate to the Modules page and check that the valid extensions there are correctly set for the corresponding modules ie PDF - .pdf, Image - .png Video - .mp4.
If not adjust that, if yes, try to run verify all on Modules page.

You could also right-click on the upload form → Insepct
then you should see the list of allowed extensions on that form, something like:

That’s generated from valid extensions set on the modules on Modules page.

Hi @Peter,

I appreciate the fast reply,

Here are my findings,

Our installation is via Docker and our CMS Version is: 1.8.11,
I already verified the extensions and all the basic extensions are ENABLED.


I already tried to VERIFY ALL modules in the Modules page, but still no luck.
And here are the filetypes under INSPECT:

I’m not sure why other file types are not showing here, maybe I’m on a different page.

Thank you very much Peter,
Please let me know if you need more details,

Should we also check our server side? if the same results reflects the CMS?

Thank you,

The upload form that you inspected seems to be the layout background upload form, which rightfully so accepts only images.

I’d expect the upload form on Library media page to have more extensions though, could you please confirm that for me?
I suspect that, it’s just the case that you didn’t look at the part of the code you wanted to in this case :slight_smile:

You could also try to stop/start your docker containers and see if that helps.

Hi @Peter,

I think this is the correct one,

Sorry for the mistake,

We already did the start/stop of the docker service, even the reboot of the whole server, but still no luck.

:frowning:

hmm in what module do you have http:// as valid extension?
At a guess that’s what breaks it for you, and of course http is not a valid file extension.

I’m not sure how else it could end up there if you don’t have it listed somewhere in valid extensions :thinking:

Hi @Peter,

It’s the WEBPAGE module,
Here it is:

I’ll try to disable it and will let you know the results,

Hi @Peter

You’re resolution works perfectly!
However what should be the correct file extension for the WEBPAGE module?
Bec. we also use webpages in our layouts, will this affect our future webpages uploads?

Thank you very much!

Hi @Peter,

No need to answer that, I just enabled the WEBPAGE module again and erase the extensions inside it. The test webpage I put still successfully opens withouth indicated file extensions in the module.

More power to your team! You are a team of marvelous people!

Have a great day Peter! you can now mark this inquiry as RESOLVED.

:slight_smile:

1 Like

I’m glad that was all there was to it.

I’ve also created an issue to improve the way we validate the valid extensions, to avoid such issues in the future - https://github.com/xibosignage/xibo/issues/1742

Webpage module does not need any valid extension entered, as valid extensions are only for files uploaded directly to the CMS library (ie videos, images, pdf etc).

1 Like