[GH-ISSUE #7995] URLs without FQDN in Web (self hosted) #3489

New issue

Open

opened 2026-03-23 21:30:41 +00:00 by mirror · 4 comments

mirror commented

2026-03-23 21:30:41 +00:00

Owner

Originally created by @mibeon on GitHub (May 27, 2025).
Original GitHub issue: https://github.com/AppFlowy-IO/AppFlowy/issues/7995

Originally assigned to: @khorshuheng on GitHub.

Hey guys,

I installed a self hosted version of AppFlowy on my ubuntu server.
Everything is working fine, except one thing.

Everything I link or upload in the desktop app works both in the desktop app and in the browser. I can click on a file in both the browser and the desktop app, and it opens in the browser. When I copy a link, it is a fully qualified domain name (FQDN) link with 'https://notes.mydomain.com/'. If I upload or link something in the browser, it only works in the browser but not in the desktop app. When I copy the link here, it is not an FQDN link. The 'https://notes.mydomain.com/' part is missing, and it starts directly with '/api/file_storage/...'. Does anyone know how I can make sure that when uploading in the browser, the media also form a full link?

Originally created by @mibeon on GitHub (May 27, 2025). Original GitHub issue: https://github.com/AppFlowy-IO/AppFlowy/issues/7995 Originally assigned to: @khorshuheng on GitHub. Hey guys, I installed a self hosted version of AppFlowy on my ubuntu server. Everything is working fine, except one thing. Everything I link or upload in the desktop app works both in the desktop app and in the browser. I can click on a file in both the browser and the desktop app, and it opens in the browser. When I copy a link, it is a fully qualified domain name (FQDN) link with 'https://notes.mydomain.com/'. If I upload or link something in the browser, it only works in the browser but not in the desktop app. When I copy the link here, it is not an FQDN link. The 'https://notes.mydomain.com/' part is missing, and it starts directly with '/api/file_storage/...'. Does anyone know how I can make sure that when uploading in the browser, the media also form a full link?

mirror added the

self-hosted

bug

labels

2026-03-23 21:30:41 +00:00

mirror commented

2026-03-23 21:30:42 +00:00

Author

Owner

@khorshuheng commented on GitHub (May 28, 2025):

Could you show us a video or a screenshot that illustrates this? I wasn't able to reproduce this issue on the managed service. Also, is the appflowy web image up to date (i.e. whether you have run docker compose pull to update the images)

@khorshuheng commented on GitHub (May 28, 2025): Could you show us a video or a screenshot that illustrates this? I wasn't able to reproduce this issue on the managed service. Also, is the appflowy web image up to date (i.e. whether you have run docker compose pull to update the images)

mirror commented

2026-03-23 21:30:42 +00:00

Author

Owner

@mibeon commented on GitHub (May 28, 2025):

Could you show us a video or a screenshot that illustrates this? I wasn't able to reproduce this issue on the managed service. Also, is the appflowy web image up to date (i.e. whether you have run docker compose pull to update the images)

Here we go.

https://github.com/user-attachments/assets/0f3671d7-e702-46d2-9b04-a2f4ac78ca0e

@mibeon commented on GitHub (May 28, 2025): > Could you show us a video or a screenshot that illustrates this? I wasn't able to reproduce this issue on the managed service. Also, is the appflowy web image up to date (i.e. whether you have run docker compose pull to update the images) Here we go. https://github.com/user-attachments/assets/0f3671d7-e702-46d2-9b04-a2f4ac78ca0e

mirror commented

2026-03-23 21:30:42 +00:00

Author

Owner

@mibeon commented on GitHub (May 28, 2025):

Could you show us a video or a screenshot that illustrates this? I wasn't able to reproduce this issue on the managed service. Also, is the appflowy web image up to date (i.e. whether you have run docker compose pull to update the images)

I run all the stuff with docker and nginx as reverse proxy for using my subdomain. The version is up to date. I installed it yesterday. I also done full images rebuilding.

Everything is working, as I said, except the issue with not having FQDN urls for stuff uploaded in the browser.

@mibeon commented on GitHub (May 28, 2025): > Could you show us a video or a screenshot that illustrates this? I wasn't able to reproduce this issue on the managed service. Also, is the appflowy web image up to date (i.e. whether you have run docker compose pull to update the images) I run all the stuff with docker and nginx as reverse proxy for using my subdomain. The version is up to date. I installed it yesterday. I also done full images rebuilding. Everything is working, as I said, except the issue with not having FQDN urls for stuff uploaded in the browser.

mirror commented

2026-03-23 21:30:42 +00:00

Author

Owner

@khorshuheng commented on GitHub (May 28, 2025):

I am able to reproduce the issue. I believe this only affect the self hoster and not the managed service. Will try to find a way to fix this.

Meanwhile, you can download the file via the download button (the right side of the block, when you hover over it) instead of clicking on the block directly or copy url.

@khorshuheng commented on GitHub (May 28, 2025): I am able to reproduce the issue. I believe this only affect the self hoster and not the managed service. Will try to find a way to fix this. Meanwhile, you can download the file via the download button (the right side of the block, when you hover over it) instead of clicking on the block directly or copy url.