Hardware: Old laptop or computer (Intel based)
YunoHost version: 22.214.171.124
**I have access to my server :Through SSH | through the webadmin | direct access via keyboard / screen
Are you in a special context or did you perform some particular tweaking on your YunoHost instance ? : no
If yes, please explain:
If your request is related to an app, specify its name and version: Friendica 2023.05~ynh3
Hi, I have installed Friendica over a recently installed and upgraded Yunohost installation. DNS services have been fully configured for my domain of type friendica.domain.tl with Friendica being the only app associated with this domain.
After arranging the required credentials and logging into the website, I get connected to friendica.domain.tl//network (i.e. with 2x a / after the hostname) rather than the expected friendica.domain.tl/network. Things seem to work, but when I select the contacts in the top menu, followed by e.g. friends under groups in the left hand menu, I end up being connected to a URL starting with https://contacts/
Interestingly, when I manually edit the URL by removing the second slash and press the same menu item, the link does connect properly (until such time the // appears again). The // also appears in my profile, which may be the reason why my other Mastodon and Friendica accounts seem not able to connect/follow me and to have my server get federated.
This URL behavior happens when connecting both from within my LAN and from the internet. My Yunohost server has all required ports forwarded from my internet router directly to my NAS, leading me to conclude it is related to how my Yunohost/nginx/Friendica handles the URL’s.
This // in the URL is not implemented on public Friendica services, and it happened on first and second install of the Friendica app, leading me to believe this may be caused by a bug in the Yunohost install scripts.
Question 1: How can I fix this myself and will this fix be sustainable with future updates? I’m not familiar enough with NGINX yet to to find the cause myself, so would need some pointers. Websearch did not help me thus far so I’m not sure how common this issue is :).
Question 2: Is this indeed caused by the script and if so, can/will that be updated?
Any hints and tips are appreciated.
Adding a little bump to keep the topic active - please comment also if you only have ideas where I might find the root of this problem. I presume it is located in one of the many nginx files being used. Thus far I can find a referral for http traffic to https, not containing any /, but none for https traffic diverting the hostname to the friendica folder as root.