xcode cloude GitLab Self-Managed connection issue - cicd

I'm trying to connect my own gitlab to the xcode cloud, but I'm stuck at registering the application.
The error message is "504 Client Timeout. If you are using a firewall, it must be configured to accept incoming connections."
If you follow this message, you need to open the firewall, but which address should you open? Or is there another way?

Related

Unable to open Public IPv4 DNS in AWS EC2 - Linux instance

I have a Spring boot project which I want to host on an AWS-EC2 instance. I was able to create its image using Git-hub, Jenkin and docker. I was also able to successfully pull and run this image in the Linux console of my AWS-EC2 instance.
According the tutorial I was following I should have been able to open the project now using the public IPv4 DNS but the response I got was that it refuse to connect.
I know that this usually has to do with Inbound rules so I added a rule to allow all traffic but it didn't help.
For anyone who wants to know:
Git-hub repository: https://github.com/SalahuddinShayan/telecom
Docker-Hub repository: https://hub.docker.com/repository/docker/salahuddinshayan/telecom
Command I used to run the image in AWS:
docker run -p8081:8081 --name final-app --link docker-mysql:mysql salahuddinshayan/telecom
Security Groups:
Networking Details:
Here is the Error:
I am completely stumped by it. Does anyone an idea on what to do to fix this?
Please check if your client is calling the right protocol, e.g. http vs https.
You are transmitting on port 8081. http://3.110.29.193:8081/ works fine from the EC2 side. 404 status is raised, so this is a client side error, not a server side error.
It means that no firewall is blocking traffic and a process (your app) was found that listens on IP:Port that you require. The problem is that the process it encountered (your app) is sending only a WhiteLabel Error Page, which is a generic Spring Boot error page that is displayed when no custom error page is present. So the issue is with the Spring app itself and not with EC2 or with connection. In other words: the traffic can reach your Spring app, but your Spring app has nothing to say in response.
As a side note, after deploying your app I would advise to refine the inbound traffic rules to allow only the traffic you want. There is no need of allowing all traffic on all ports.

Google Cloud Platform SSH error code 1006

I made an instance and connected SSH in my project. My project is for machine learning, so I opened jupyter notebook and ran it. But the terminal always sends me an error like this.
"Connection via Cloud Identity-Aware Proxy Failed
Code: 1006
Please ensure you can make a proper https connection to the IAP for TCP hostname:https://tunnel.cloudproxy.app.
You may be able to connect without using the Cloud Identity-Aware Proxy."
I have tried to create firewall rule but this doesn't work.
Someone says that this is because of session timeout. If it is, what can I do to solve it?

unable to publish clickonce application on aws ec2 through ftp in load balancer

Recently I installed SSL using ZeroSSL on my website and for doing that I had to deploy Load Balancer for my EC2 instance (IIS 10). I was initially using ftp to directly publish my ClickOnce application. But now I am not able to publish my application. It shows:
Failed to connect to 'ftp://website/folder' with the following error: Unable to create the Web site 'ftp://website/folder'. The server unexpectedly closed connection.
On the other hand I am able to connect via telnet to the server. But I am unable to connect via file explorer, it shows connection timed out.
Is it possible to do ftp publish through aws Load Balancer? If yes then, please point me in correct direction. And if no, what are other options?
Thanks a lot for taking time to answer and read my question!
PS. Please do let me know if you want any other details.

VPN connection to Amazon RDS with openvpn suddenly fails

I set AWS Client VPN Endpoint, and downloaded opvn file, configured it to refer to cert/key files and connected to AWS RDS.
It used to success connecting yesterday, but today, after re-installing ESET security app
It shows the following error when I trying connecting with MySQL client app:
ERROR 2005 (HY000): Unknown MySQL server host 'myrds.something.ap-northeast-1.rds.amazonaws.com' (0)
I am not sure how to detect the cause of the error. If I configured RDS settings to pubilc, the error above not shown and just waiting for minutes...
(maybe I guess some DNS settings overriden by ESET? )
You can easily debug the problem:
AWS Client VPN Endpoint, You can see the active connection. See if you are connected to it or not.
Do you restarted or reinstall RDS also, Because it will change the URL to connect.
Is username/password of DB is changed.
If RDS is in public setting you don't even need a VPN connection.
Also as suggested above check VPN to RDS VPC Route.
Thanks,
AB
here are some troubleshooting steps.
When you connect your VPN:
Check if it's pushing the DNS server address via DHCP configuration
Check if new routes are added to your route table. you can do "route print" in the windows command line
Hope this helps.

AWS IoT Mosquitto Certificate Error

I'm running into a really frustrating error with trying to bridge mosquitto to the AWS IoT MQTT system. I set it up following this guide:
https://aws.amazon.com/blogs/iot/how-to-bridge-mosquitto-mqtt-broker-to-aws-iot/
Which at first seemed to work. I was able to see messages in he AWS IoT console when I subscribed to it. Then I restarted mosquitto and I'm just getting this error over and over again:
1529722121: OpenSSL Error: error:14094416:SSL routines:ssl3_read_bytes:sslv3 alert certificate unknown
1529722121: Socket error on client local.bridgeawsiot, disconnecting.
1529722151: Bridge local.bridgeawsiot doing local SUBSCRIBE on topic localgateway_to_awsiot
1529722151: Bridge local.bridgeawsiot doing local SUBSCRIBE on topic both_directions
1529722151: Connecting bridge awsiot (a10cxxxxxxxxxx.iot.us-west-2.amazonaws.com:8883)
1529722182: Connecting bridge awsiot (a10cxxxxxxxxxx.iot.us-west-2.amazonaws.com:8883)
I've verified multiple times that the certificates that I'm using are the correct ones, I've also checked that the Thing has a policy attached to it and that the certificates are activated. I made sure that the rootCA.pem file is the one issued from Verisign. I'm at a loss as to why the broker is not working. The host OS is Ubuntu 18.04 running the bundled version of mosquitto. Any help would be appreciated.
I figured out what the issue was. I was using the CLI to retrieve my IoT endpoint and my default region was set to us-west-2. The certificates that I created are in us-east-1.