Both spinnaker and bitbucket located inside private subnet scheme. Spinnaker is deployed on kubernetes. When I try to test connection it gives this error:
http://spinnaker-mydomain.com:8084/webhooks/git/bitbucket
java.lang.IllegalStateException: Request cannot be executed; I/O
reactor status: STOPPED
when I try to test connection from telnet it closes as well saying connection refused.
Wondering weather it has something to do with authentication or there is problem in bitbucket service
If you're using BitBucket on-prem, use the url:
http://spinnaker-mydomain.com:8084/webhooks/git/stash
Related
I am attempting to deploy a CloudFormation template, but the Internet Gateway resource fails with an encoded error that decodes to:
Failed to connect to proxy URL: "http://127.0.0.1:10080"
What proxy am I missing that would prevent an Internet Gateway from being created?
It turns out the proxy error is misleading. The real issue is that the user deploying the CloudFormation template did not have the correct permissions.
I granted the user the AmazonVPCFullAccess policy, and the template was deployed correctly.
I am using docker compose to spin up an api, along with Dapr for state management and a local cosmosDB emulator.
When specifying my local azure cosmosDB as the state store in my local Dapr component, the Dapr container fails to start with the error message:
level=warning msg="error initializing state store cosmosdb (state.azure.cosmosdb/v1): Post "https://localhost:8081//dbs": dial tcp 127.0.0.1:8081: connect: connection refused"
If I change the Dapr component to point at my cosmosDB in azure the Dapr container works fine, so I know this is an issue with cosmosDB locally. Im new to dapr and cosmos db but I'm not sure what I'm missing.
Since you are using https do you have a self-signed certificate? this might be because of SSL exception.
Also, check if your local Azure Cosmos DB Emulator is running or not by navigating to the below url:
https://localhost:8081/_explorer/index.html
Checkout some related issues: here, here, here try closing and restarting the emulator sometime.
According to Configuring the Artifactory Service Endpoint, an artifactory instance as service endpoint need to be configured. One of the parameter is the server URL to the artifactory. What if the server URL is a local intranet, will the URL be considered valid ? I am having error with the URL I am providing (Local intranet). The error is:
"Failed to query service connection.....Error Message:'An error
occurred while sending the request'"
What if the server URL is a local intranet, will the URL be
considered valid ?
While the server URL you used here is a local internet, which means our azure image(Hosted agent) could not get communicate with it from public internet. That's why the error message told you failed to send request to server.
So, here the best way is you need configure one self agent in that local machine.
BUT, if Hosted agent is one preferred choice in pipeline execution. I'm afraid you have to configure your artifactory instance to make it accessible from the internet, just like the URL in the blog you shared above. Because our Hosted agent actually is Azure VM which hosted in cloud.
I can't connect from azure resource (aks node) to Azure postgres using pgcli. I also tried directly from node and got the same error message:
FATAL: Client from Azure Virtual Networks is not allowed to access the server. Please make sure your Virtual Network is correctly configured.
Firewall rules in the resource are on:
Allow access to Azure services: ON
Running the same pgcli login command on my computer and on another azure resource seems to work fine.
Adding Firewall rules to all IPs return the same error.
Curl from the problematic server (host:5432) returns a reply, so it's not an outbound issue.
What does the error mean?
A VM where the connection originates from is deployed to a virtual network subnet where Microsoft.Sql service endpoint is turned on. Per documentation:
If Microsoft.Sql is enabled in a subnet, it indicates that you only want to use VNet rules to connect. Non-VNet firewall rules of resources in that subnet will not work.
For connection to succeed there must be a VNet rule added on PostgreSQL side. At the time the question was asked VNet Service Endpoints for Azure Database for PostgreSQL just got to public preview so I assume it might not have been available for the OP.
Solution
As of November 2020, Service Endpoints for Postgres is GA and instead of disabling the service endpoint one can add a missing VNet rule to the PostgreSQL server instance and reference the service endpoint-enabled subnet. It can be done via Portal or Azure CLI
Apparently, the vm is part of a vnet that a service endpoint tag Microsoft.sql was enabled.
I found this answer. To solve the problem I disabled the service endpoint and added the public IP to the Connection Security section.
I encountered the same problem.
All I did was to switch Allow access to Azure services to ON .
I'm trying to deploy a service fabric application to an unsecure Azure Service Fabric cluster. When I open the publish window in VS 2017 I get the following. If my cluster is unsecure, shouldn't I be able to publish it w/o configuring the cert?
I tried a publish anyways and I got:
Try accessing the server via powershell to maybe get a better error. Usually, errors like this are caused by firewalls blocking the port 19000.