this post was submitted on 23 Oct 2025
361 points (98.9% liked)

Selfhosted

62187 readers
488 users here now

A place to share alternatives to popular online services that can be self-hosted without giving up privacy or locking you into a service you don't control.

Rules:

Detailed Rules Post

  1. Be civil.

  2. No spam.

  3. Posts are to be related to self-hosting.

  4. Don't duplicate the full text of your blog or readme if you're providing a link.

  5. Submission headline should match the article title.

  6. No trolling.

  7. Promotion posts require active participation, with an account that is at least 30 days old. F/LOSS without a paywall has exceptions, with requirements. See the rules link for details. Tags [CBH] or [AIP] are required, see the links in Rule 8 for details.

  8. AI-related discussions and AI-involved promotional posts have additional requirements for tagging, as noted in Rule 7 and the AI & Promotional Post Expanded Rules post, and find example disclosures here.

Resources:

Any issues on the community? Report it using the report flag.

Questions? DM the mods!

founded 3 years ago
MODERATORS
 

Has this impacted your self hosted instances of Immich? Are you hosting Immich via subdomain?

Related:

you are viewing a single comment's thread
view the rest of the comments
[–] FreedomAdvocate 0 points 11 months ago (1 children)

The issue they had was being marked as phishing, not the SSL certificate warning page.

Have you seen what browsers say when you have a look at the SSL certificate warning page?

It is for pull requests. A user makes a change to the documentation, they want to be able to see the changes on a web page.

Why is a user made PR publishing a branch to Immich's domain for the user to see?

[–] BCsven@lemmy.ca 1 points 10 months ago (1 children)

I thought that was how pull requests worked, its a branch if you'veade a departure to edit code, you have the pull request and ask them to merge into the main branch. It should be visible to everyone so everyone can review the change.

[–] FreedomAdvocate 1 points 10 months ago

The branch for the PR shouldn't be hosted on the production site's domain, and that deployment that the company will be testing and reviewing shouldn't be accessible to the public. They even have internal in the URL, while being accessible by external people lol