Thank you! It seems the ongoing 3.35 version is reimplementing the auto-upload logic, so this is promising. It is still in RC stage, but hopefully will be stable soon.

What’s the link to the issue? I’d like to follow its progress. Thank you!

Is this really a case of conflict of interest though?

That’s already my SSID, please don’t use it too

Microsoft has an additional requirement where “_optout” has to be somewhere in the SSID (not necessarily at the end). This was detailed in a now deleted support post.

Who is this request for feedback open to?

Same, using the default storage template.

I’ve not been able to make it work reliably with photos backed up using immich on my android phone, is if working for you? I read somewhere storage templates are not very robust/reliable.

If they have an issue with copyright infringement, they should discuss with OpenAI, Microsoft, Google, Anthropic and more.

I salute the effort, but it would really drive the point home if you also tracked changes to the settings available as well, as in settings disappearing and new settings appearing. The default values for those new settings is also crucial, and finding out about a setting no longer being available could also be useful.

Interesting setup. Funnily, I have one specific subdomain hosted on an actual cloud provider, publicly and all other subdomains are private and local. It works just fine :)

In the end, there’s like a tradeoff between enjoying your system as is and pouring I don’t know how many hours in setting it up when it’s a new idea haha

I’m not trying to expose it to the internet and there are indeed multiple solutions to get HTTPS. This one works with a real domain name is what works best for me :)

Yes it does. Are you using Firefox? And you can’t resolve local ip addresses, so that’s why you are setting this exception?

Wouldn’t that require me to use tailscale even at home on my home network? It also does not provide HTTPS unless you maybe use magic DNS, but then we’re back to using a public domain I guess.

Since it knows the DNS will always be public, it also knows that the 192.168.10.20 address is not routable on the internet where it found it.

That is in fact not it. I left the default firefox DNS setting. I simply enabled network.trr.allow-rfc1918 from within the about:config which allows the resolution of local IP addresses. It now works. All my DNS are public, I make no use of any private, local DNS.

This was not required in my case, but maybe it solves other issues?

Works flawlessly with my tailscale setup :) Thanks for asking! I’m not trying to expose anything to the open. Just for me personally, from home or remotely using my VPN.

Thanks for your response. Indeed, this is only for myself within my home network. No split DNS required, the public DNS record mentions my local private IP address which of course will only resolve to my homeserver from within my home network and will not lead anywhere for anyone else from any other network. That’s all what makes this great. Yes, I did the DNS challenge as I mentioned in my OP and retrieved a wildcard certificate for all my local needs :)

Yes, I now managed to make it fully work on firefox too, needed to set network.trr.allow-rfc1918 to true in the about:config settings! :)

so some apps (like Firefox) with internal hard-coded DNS functions

Thank you! This was the information I needed! It landed me on this page https://support.mozilla.org/en-US/kb/firefox-dns-over-https which shows When DoH is enabled, Firefox by default directs DoH queries to DNS servers that are operated by a trusted partner, which has the ability to see users' queries and lead me to this page https://wiki.mozilla.org/Trusted_Recursive_Resolver where I was able to read more about it. That explains why it does not work, I appreciate the insight!