Skip to content
By using AWS re:Post, you agree to the AWS re:Post Terms of Use
AWS re:Postre:Post
About re:Post

Error 502 bad gateway occurred + while using aws-samples/dcv-web-portal. Please provide additional solutions to the error. how to connection dcv server?

0

Hello, I am a junior developer. To build dcv infrastructure, I successfully deployed to ap-northeast-2 based on https://github.com/aws-samples/dcv-web-portal. Also, after connecting to the front-end, I received the load balance link and connected, but 502 bad gateway occurred. I'm stuck here and can't find a solution. They say you can ask questions directly on GitHub, but since questions are also blocked, this is the only place to ask questions. I would appreciate your help. Also, the created instance keeps dying and I don't know how to finally connect to dcv. Additionally, the health status of the target group is normal

Topics
ServerlessFront-End Web & MobileComputeNetworking & Content Delivery
Tags
Amazon API GatewayNICE DCVElastic Load Balancing
Language
English
asked 2 years ago588 views
2 Answers
1

Hello.

You may want to check the troubleshooting methods listed in the README.
https://github.com/aws-samples/dcv-web-portal?tab=readme-ov-file#-troubleshooting

  • First verify there are some instances available and healthy in the Target Groups. You should see at least one instance with the name [NICE DCV] Connection Gateway
  • If this is not the case, make sure the Auto Scaling Group has 1 (or more) as desired/minimum capacity.
  • If there are some instances, connect to them via the Connect button (and Session Manager) in the EC2 console.
  • Then type the following commands:
    • sudo su -
    • systemctl status dcv-connection-gateway. It should return a status active.
  • If the status is inactive, type the following command:
    • systemctl restart dcv-connection-gateway
  • You can further analyze the issue with the logs available in /var/log/dcv-connection-gateway/gateway.log
EXPERT
answered 2 years ago
EXPERT
reviewed 2 years ago
  • Zeus_0220
    2 years ago

    [NICE DCV] Is it correct to connect to the Connection Gateway instance? My [NICE DCV] Connection Gateway instance did not have dcv installed. Could this be the cause? It comes out as below. What additional settings should I configure? Also, when you access a website created with cloudfront and lanching an instance, the instance is terminated while being created and continues in the FINALISING state indefinitely. [root@ip-192-168-2-245 log]# systemctl status dcv-connection-gateway Unit dcv-connection-gateway.service could not be found.

  • Riku_Kobayashi EXPERT
    2 years ago

    Will it work if I deploy it on us-east-1 instead of ap-northeast-2?

  • Zeus_0220
    2 years ago

    [NICE DCV] I connected to the Connection Gateway instance and checked that active was displayed normally using the systemctl restart dcv-connection-gateway command. However, when I opened /var/log/dcv-connection-gateway/gateway.log, there was the following error. According to chatgpt, it is either a tls certificate error or a backend service connection failure error. However, the certificate was in the correct location. But I don't know what back-end services should be inspected.

  • Zeus_0220
    2 years ago

    Jun 19 04:12:46.036 INFO HTTP: New incoming connection from 111.111.11.111:51600 | Splicer Connection ID: 13 Jun 19 04:12:46.037 INFO HTTP: New incoming connection from 111.111.11.111:51599 | Splicer Connection ID: 14 Jun 19 04:12:46.233 WARN HTTP:Splicer Connection{id=13 client_address="111.111.11.111:51600"}: Error in connection task: TLS handshake error: received fatal alert: CertificateUnknown Jun 19 04:12:46.233 WARN HTTP:Splicer Connection{id=13 client_address="111.111.11.111:51600"}: Certificate error: AlertReceived(CertificateUnknown) Jun 19 04:12:46.233 WARN HTTP:Splicer Connection{id=14 client_address="111.111.11.111:51599"}: Error in connection task: TLS handshake error: received fatal alert: CertificateUnknown Jun 19 04:12:46.233 WARN HTTP:Splicer Connection{id=14 client_address="111.111.11.111:51599"}: Certificate error: AlertReceived(CertificateUnknown) Jun 19 04:12:46.449 INFO HTTP: New incoming connection from 112.221.39.134:51602 | Splicer Connection ID: 15 Jun 19 04:12:46.655 INFO HTTP:Splicer Connection{id=15 client_address="111.111.11.111:51602"}:WebResources: Serving request GET / Jun 19 04:12:46.655 INFO HTTP:Splicer Connection{id=15 client_address="111.111.11.111:51602"}:WebResources: Routing request to http://localhost:8081/static/. Jun 19 04:12:46.655 INFO HTTP:Splicer Connection{id=15 client_address="111.111.11.111:51602"}:WebResources: Request does not have 'Origin' header Jun 19 04:12:46.655 INFO HTTP:Splicer Connection{id=15 client_addr

  • Zeus_0220
    2 years ago

    Jun 19 04:12:46.655 INFO HTTP:Splicer Connection{id=15 client_address="111.111.11.111:51602"}:WebResources: Unable to connect: error sending request for url ([obfuscated] http://localhost:8081/static/): errortrying to connect: tcp connect error: Connection refused (os error 111) Jun 19 04:12:46.655 INFO HTTP:Splicer Connection{id=15 client_address="111.111.11.111:51602"}: Served GET / 502 Bad Gateway took 0ms, user agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/126.0.0.0 Safari/537.36

0

Not sure if this helps.

AWS has released NICE DCV Access Console, which is a new web-based solution for administrators and end users to more easily manage their remote desktop sessions.

Documentation is at https://docs.aws.amazon.com/dcv/latest/access-console/what-is-access-console.html

AWS
EXPERT
answered 2 years ago

You are not logged in. Log in to post an answer.

A good answer clearly answers the question and provides constructive feedback and encourages professional growth in the question asker.

Relevant content