If so, you’d want to add a label to tell traefik which network to use; if memory serves, I think it is literally traefik.docker.network=traefik_default or something like that, where traefik_dedault should reflect the network the service is sharing with traefik — I put mine on the traefik default network from docker compose, hence the name but you may have other design.
Edit: sorry I’m on mobile right now, and I just saw you do have traefik docker network bit already, but it says media. Is that network where traefik have access?
Cool. Thanks! One less reason for me to even consider Porman on the radar. Personally, I really don’t care for the tool itself, and am way more interested in the apps that I can run and play with :)
If docker works for you, then don’t change what’s not broken. If there are things you don’t like about docker (root access etc for example) then venture out and try others. At the end of the day, they’re just tools to get to the more interesting stuff — actually running applications and playing with them.
Cool. So don’t use their app. I’d imagine HomeAssistant usage cannot be tracked as it wouldn’t go through their app.
FWIW, I’m all in on HomeKit, so I only control over Home app for my light switches from another vendor, and I’ve got no skin in the game with Leviton, but same idea applies. No vendor apps means their app based tracking are much less relevant.
Seems to be more on the web side of things for affiliate marketing, not necessarily light switch usage patterns? At least the pasted/quoted bit doesn’t suggest that it’d cover interactions with the devices.
Does Wireguard have a centralized server that the server at home connect to in order to expose itself? If not, I don’t see how it’d work for OP, because at this point, based on info shared, I’m inclined to think OP is having trouble exposing ports (be it ISP imposed or knowledge gap) as opposed to having issue with the service / vendor.
521 = Origin server down; I.e. the port is not open and/or the IP address is incorrect all together.
522 = Origin server time out; I.e. the port might be open but no content is being sent back.
If you’re seeing 521, then Cloudflare cannot establish a connection to port 80/443 on your IP address in the A record. Bearing in mind that in order for someone from outside of your LAN (i.e CloudFlare) to have access to your services, they must be able to reach the service, so this value should be your external IP address, not an internal address. Once you have your external address keyed into the record, have someone else not in your home try to access that IP/port combination and see what happens. If they cannot access, then port forwarding is not setup or your ISP is blocking, or you’re behind some CGNAT. If they can access, then something else is at play (origin IP filtering comes to mind).
521 usually means they cannot reach your server properly. Was the router change due to a new ISP, and does the new ISP block port 80/443? Did you re-make all the relevant port forwarding rules? Changing CDN won’t change anything if your ports are closed/not responding as expected.
Was going to say "another one of these?" but, wow, the article really further highlights the childish nature of the Lemmy devs... Can't wait for Sublinks to reach feature parity and become main stream, so we can leave this dark phase behind.
This has nothing to do with search. Just advertising. They’ll remain in search results as long as they don’t take the page down and remain otherwise complaint with search policies.
No one needs to pay to put ads next to content they don’t agree with. Google is informing them that advertisers don’t want their ads on these pages. They don’t have to remove the pages, thereby not being censored, they’d just suffer the consequence of not getting ad revenue.
The communication suggests this is coming from Google AdSense which is the publisher advertising side of things, informing the site admin that their site contains content that will likely result in them being removed from being eligible to sell ad slots to advertisers on their network.
Whether or not the assessment of individual flags are correct is another discussion (of which I genuinely don’t care and don’t have time to look into), but it is perfectly normal and acceptable for ad exchanges, Google AdSense in this case, to inform publishers that they’re about to lose out on profit potential because their content is not in compliance with what the advertisers are expecting from the exchange.
Google AdSense could just as easily immediately kick the publisher from the program, at which point they’d no longer be eligible to sell ads through AdSense, but their content will continue to remain online. No censorship is taking place here.
One downvote from the OP to troll; one downvote from the troll to OP; ten downvotes from the troll’s arsenal of alts to OP; hundreds of downvotes to the troll from the community.
Reddit with their quirks and issues have at least demonstrated it’s fine for the most part. Established communities can identify trolls quickly, make them easier to spot for moderators through voting, and enable moderation tools to act and block quickly. Whereas the current Lemmy system feels like burying their head in the sand, and pretending trolls can’t exist because only admins can, through convoluted queries, see the users’ historical vote aggregate.
In the future, please use cross post instead and not click bait titles into different communities.
On a more related note, do you have knowledge if the image was federated outwards? I’m fairly sure I’ve subscribed to that community, so there may be an off chance I have received a copy of the image as part of federation. Is there any way to scour other instances to find images that is federated out and needs to be removed?
Good luck. The Lemmy devs took out total votes on profiles so people cannot see in aggregate how communities have viewed individual users in some lofty goal to be neutral. You’ll have to bend their arms backward for them to reintroduce some sort of aggregate score/trust.
chiisana @ chiisana @lemmy.chiisana.net Posts 4Comments 500Joined 2 yr. ago
Do you have more than one network in Docker?
If so, you’d want to add a label to tell traefik which network to use; if memory serves, I think it is literally
traefik.docker.network=traefik_defaultor something like that, wheretraefik_dedaultshould reflect the network the service is sharing with traefik — I put mine on the traefik default network from docker compose, hence the name but you may have other design.Edit: sorry I’m on mobile right now, and I just saw you do have traefik docker network bit already, but it says media. Is that network where traefik have access?