I build a CSV file using the marketplace plugin list2csv method, and then open a new browser window to the created CSV, which triggered a download -
This as worked fine for months/years, but stopped working in the last few days or so. I can see the files from the console, and if I access the backendless link for the file, it gets downloaded. I can’t seem to access it through my custom domain any longer.
Hello @Tim_Jones
Thanks for the report! To help us investigate, could you clarify a few things:
Steps to reproduce – Can you describe the exact sequence of actions that leads to the error? (e.g., trigger the plugin → call list2csv → open URL → error appears)
File name / path – What is the name or path of the CSV file being generated? Does the error occur with any file, or only specific ones?
Custom domain URL – What does the URL look like when you try to open the file through your custom domain? (You can redact sensitive parts)
Screenshot clarification – In the screenshot you attached, which service/method is shown? Is it the list2csv call itself, or the subsequent file open/download step?
Recent changes – Were there any changes on your end around the time this stopped working (domain settings, SSL certificate, etc.)?
The Backendless file URL still works, so the issue seems to be specific to the custom domain routing — any additional context would help narrow it down quickly.
Regards,
Volodymyr
Thanks for the response, @Volodymyr_Ialovyi.
I’ve been testing and it seems related to accessing anything from the custom domain.
If a file is in the root, should I be able to access it at CustomDomain.com/filename.ext?
I uploaded a file to the root directory and cannot access it as described.
Tim
Hello @Tim_Jones
Thanks for testing that — this helps narrow it down.
With a Backendless custom domain, files are typically accessed through the File Service path. Even if the file is located in the root folder of the File Service, the URL usually looks like this:
https://YourCustomDomain.com/api/files/filename.ext
Could you try accessing the file using that format and see if it works?
Since you mentioned that files can still be downloaded using the Backendless file URL, but anything accessed through the custom domain fails, the issue is likely related to the custom domain routing or configuration.
Could you please also confirm:
You can also double-check the setup steps here: Custom Domains
Regards,
Volodymyr
I can access this file -
I use to be able to access the file at mydomain.com/testCSV.csv.
This has stopped working in the past few days. I haven’t made any changes, which is the confusing part on my end.
TIm
Good question.
No, File Repository access does not need to be enabled for files to be publicly accessible. If a file is stored in the File Service and not restricted by permissions, it can be accessed directly via its URL.
The URL you shared:
https://backendlessappcontent.com/.../files/testCSV.csv
works because it is the direct Backendless file URL, which bypasses the custom domain.
Regarding the setting shown in your screenshot — the tooltip there mentions:
“This is the domain that will be used to generate URLs for the files uploaded to your Backendless File repository.”
This setting simply defines which domain Backendless uses when generating file URLs. It does not affect whether the file repository itself is accessible.
When using a custom domain, files are normally accessed through the File Service path, for example:
https://mydomain.com/api/files/testCSV.csv
If possible, could you check whether this URL works for you?
You can also review the custom domain setup here to make sure everything matches the expected configuration: Custom Domain
Regards,
Volodymyr
I am able to access the file adding /api/files/ to the path.
Nothing on my end has changed. It use to work just fine and then stopped working. I am updating my code to add /api/files/ to the paths, it is just strange that it stopped working and you don’t know why. I am assuming you changed something.
Tim
Hello @Tim_Jones
Please let me know what value is set for your domain in the Custom Domain settings.
Regards,
Inna
By default, domains open files located in the web directory and its subdirectories. Therefore, to ensure that the link opens at the path you specified, you need to place your file in the web folder.
If the file is located in this directory or any subdirectories below it, you need to use /api/files/
Regards,
Inna
Hi Inna,
I tested and was able to access a test.jpg at mydomain.com/test.jpg by putting the file in the web folder.
If I have a folder in root, and want to access it I use /api/files and that starts at the root level?
If this is the root directory -
/web
/other_files
I would access anything in /web at mydomain.com/filename.ext and anything in other files at mydomain.com/api/files/other_files/filename.ext?
It is good to understand how it works now, but frustrating no one has explained why working behavior stopped working.
Tim
Hi @Tim_Jones ,
If I have a folder in root, and want to access it I use /api/files and that starts at the root level?
Yes, correct. after /api/files. If file test.jpg located in the root then path will be mydomain.com/api/files/test.jpg. If file is located in directory testDir which itself located in the root then path will be mydomain.com/api/files/testDir/test.jpg
If this is the root directory -
/web
/other_files
I would access anything in /web at mydomain.com/filename.ext and anything in other files at mydomain.com/api/files/other_files/filename.ext?
Yes, correct.
It is good to understand how it works now, but frustrating no one has explained why working behavior stopped working.
Behavior, on which you relied before, was not supposed to work at all. Most probably that there was a bug in routing which was fixed by other changes which were made.
Access to files outside web directory should be done via /api/files in case of custom domains as described here
For files inside of web directory you can omit that part.
Regards, Andriy
Thank you for the concise answer, @Andriy_Konoz.
Best,
Tun
