Share this… Facebook Twitter Linkedin Telegram Messenger Hackernews Service Groups Architecture Overview Service Groups Deep Dive Infrastructure Perspective Definition and PurposeAzure Service Groups ...

I used this command to stop it (replaced the sub-id): az network application-gateway stop --id /subscriptions/sub-id/resourceGroups/load-balancer-resources/providers/Microsoft.Network/applicationGateways/ipro-application-gateway-load-balancer The output was this (same as before): - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Processing /etc/letsencrypt/renewal/ipro.rest.conf - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Certificate is due for renewal, auto-renewing... Plugins selected: Authenticator nginx, Installer nginx Simulating renewal of an existing certificate for ipro.rest and www.ipro.rest Performing the following challenges: http-01 challenge for ipro.rest http-01 challenge for www.ipro.rest Waiting for verification... Challenge failed for domain ipro.rest Challenge failed for domain www.ipro.rest http-01 challenge for ipro.rest http-01 challenge for www.ipro.rest Certbot failed to authenticate some domains (authenticator: nginx). The Certificate Authority reported these problems: Domain: ipro.rest Type: connection Detail: 172.206.168.127: Fetching http://ipro.rest/.well-known/acme-challenge/C_sBKMg3sZ6PgslxIf8wH0VYS8hilXINRujM8Cq5CYQ: Timeout during connect (likely firewall problem) Domain: www.ipro.rest Type: connection Detail: 172.206.168.127: Fetching http://www.ipro.rest/.well-known/acme-challenge/ppBbbR337OgRKmlvlGISYhlYlky23TqtX5JiTdCgLr8: Timeout during connect (likely firewall problem) Hint: The Certificate Authority failed to verify the temporary nginx configuration changes made by Certbot. Ensure the listed domains point to this nginx server and that it is accessible from the internet. Cleaning up challenges Failed to renew certificate ipro.rest with error: Some challenges have failed. - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - The following simulated renewals succeeded: /etc/letsencrypt/live/ipro.monster/fullchain.pem (success) The following simulated renewals failed: /etc/letsencrypt/live/ipro.rest/fullchain.pem (failure) - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 1 renew failure(s), 0 parse failure(s) I'm still pretty new to this, so I'm not sure how to set up the DNS properly, is there a resource you could guide me towards? I also saw something about ipv4 vs tcp6 protocols, and I can confirm that the port 80 on my VM is using tcp6, I don't know if that's a real issue or not

Azureにdocker-composeでNode-REDのインスタンスを作っておくときメモ Node-REDのインスタンスを作るメモです。 流れとイメージ リソースグループの作成 サービスプランの作成 インスタンスの作成 リソースグループが一番大きなフォルダ、サービスプランを1つのフォルダとしてサービスプランの中にインスタンスがぶら下がっているイメージ。 サービスプランひとつにたくさんのインスタンスのぶらさげたらCPU負荷がやばかったので安いプランを使うときはサービスプランの中に大量インスタンス作成を避けておく。 準備 リソースグループとサービスプランは事前にあればそれを使うでもOKだけど1から作る場合メモです。 リソースグループを作っておく 管理用にリソースグループを作っておきます。 普段は管理画面からやりますがメモ的に。 $ az group create --name myResourceGroup --location japaneast { "id": "/subscriptions/xxxxxxxxxxxxxxxxxxxxx/resourceGroups/2025-protoout", "location": "japaneast", "managedBy": null, "name": "2025-protoout", "properties": { "provisioningState": "Succeeded" }, "tags": null, "type": "Microsoft.Resources/resourceGroups" } サービスプランを作っておく az appservice plan create --name プラン名 --resource-group リソースグループ名 --sku スケールプラン --location リージョン こんな感じ B1で作る場合は以下のような感じ az appservice plan create --name myLinuxPlan --resource-group myResourceGroup --sku B1 --is-linux --location japaneast …

Burning Data with Malicious Firewall Rules in Azure SQL Server > The next rule we created was named “../”, and upon deleting that rule, the entire test SQL Server was also suddenly deleted, and we found ourselves in need of a new test server! > The cause of the deletion of our test server can be found in the URL to which the DELETE request is sent. The URL the DELETE request was sent to is: > /subscriptions/<subscriptionId>/resourceGroups/<rg>/providers/Microsoft.Sql/servers/test-4ad9a/firewallRules/../?api-version=2021-11-0. > The firewall rule name “../” within the URL is treated as if it refers to the parent directory and to the SQL Server itself, which leads to the entire server being deleted. > **With a little effort, it’s possible to create a rule that deletes any resource in the Azure tenant with the following name:** > **../../../../../../../ <theResourceURL>?api-version=<relevant_version>#”.** Little Bobby Tables strikes again

i could imagine that it has something to do with the uid-changes

You may find more help from the developer of the plugin directly if you go through their issues system I’m guessing this is the plugin you are talking about? GitHub ### derkork/godot-resource-groups An add-on for the Godot engine that simplifies handling of resources - derkork/godot-resource-groups

Yeah that’s the one! I probably should go to them directly, makes much more sense than the forums haha. I’ll see if I can drop an issue in there, hopefully it can get fixed fast! I can’t imagine its a difficult problem to fix

Hi everyone, I wanted to share a common challenge we’ve encountered in DevOps pipelines when working with Azure Service Fabric Managed Clusters (SFMC) — and open it up for discussion to hear how others are handling it. 🔍 The Issue When retrieving the cluster certificate thumbprints using PowerShell: (Get-AzResource -ResourceId "/subscriptions/<SUBSCRIPTION_ID>/resourceGroups/<RG_NAME>/providers/Microsoft.ServiceFabric/managedclusters/<CLUSTER_NAME>").Properties.clusterCertificateThumbprints …it often returns multiple thumbprints. This typically happens due to certificate renewals or rollovers. Including all of them in your DevOps configuration isn’t practical. ✅ What Worked for Us We’ve had success using the last thumbprint in the list, assuming it’s the most recently active certificate: (Get-AzResource -ResourceId "/subscriptions/<SUBSCRIPTION_ID>/resourceGroups/<RG_NAME>/providers/Microsoft.ServiceFabric/managedclusters/<CLUSTER_NAME>").Properties.clusterCertificateThumbprints | Select-Object -Last 1 This approach has helped us maintain stable and secure connections in our pipelines. 🔍 Solution 2: Get current Server Certificate You can also verify the active certificate using OpenSSL: openssl s_client -connect <MyCluster>.<REGION>.cloudapp.azure.com:19080 -servername <MyCluster>.<REGION>.cloudapp.azure.com | openssl x509 -noout -fingerprint -sha1 🛠️ Tip for New Deployments If you're deploying a new SFMC, consider setting the following property in your ARM or Bicep template: "autoGeneratedDomainNameLabelScope": "ResourceGroupReuse" This ensures the domain name is reused within the resource group, which helps reduce certificate churn and keeps the thumbprint list clean and manageable. ⚠️ Note: This setting only applies during initial deployment and cannot be retroactively applied to existing clusters.

Service Features: aws-sdk-quicksight (1.22.0): Adding IAMIdentityCenterInstanceArn parameter to CreateAccountSubscription aws-sdk-resourcegroups (1.19.0): Added a new QueryErrorCode RESOURCE_TYPE_...