CloudFront
tcp/80
Open service 18.173.154.92:443 · api.dev.myqsrsoft.com
2026-01-12 03:48
HTTP/1.1 403 Forbidden
Content-Type: application/json
Content-Length: 42
Connection: close
Date: Mon, 12 Jan 2026 03:48:37 GMT
X-Amzn-Trace-Id: Root=1-69646f15-6b53f9e771a1c63b2fd110f7
x-amzn-RequestId: 8d343726-e5ea-4007-a82c-0e03dcc6ae6e
x-amzn-ErrorType: MissingAuthenticationTokenException
x-amz-apigw-id: XDZLaEBdoAMEc0w=
X-Cache: Error from cloudfront
Via: 1.1 fe6d656eba9969a63bb94889f81e9bf8.cloudfront.net (CloudFront)
X-Amz-Cf-Pop: MUC50-P3
X-Amz-Cf-Id: CPviCWLBUPluXcV1qAxRTtQiNBvlCz6FUI6HlUPP16UttErSKREAdg==
{"message":"Missing Authentication Token"}
Open service 18.173.154.24:80 · api.dev.myqsrsoft.com
2026-01-12 03:48
HTTP/1.1 403 Forbidden Server: CloudFront Date: Mon, 12 Jan 2026 03:48:37 GMT Content-Type: text/html Content-Length: 915 Connection: close X-Cache: Error from cloudfront Via: 1.1 7ad01e16cb039e6f25a50f4e294fd0ae.cloudfront.net (CloudFront) X-Amz-Cf-Pop: MUC50-P3 X-Amz-Cf-Id: FXbt9EywfEGvdubVlZiFKgTT3YmqEtSrU0yVR32uMrk6iLjPVbPRBA== Page title: ERROR: The request could not be satisfied <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd"> <HTML><HEAD><META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1"> <TITLE>ERROR: The request could not be satisfied</TITLE> </HEAD><BODY> <H1>403 ERROR</H1> <H2>The request could not be satisfied.</H2> <HR noshade size="1px"> Bad request. We can't connect to the server for this app or website at this time. There might be too much traffic or a configuration error. Try again later, or contact the app or website owner. <BR clear="all"> If you provide content to customers through CloudFront, you can find steps to troubleshoot and help prevent this error by reviewing the CloudFront documentation. <BR clear="all"> <HR noshade size="1px"> <PRE> Generated by cloudfront (CloudFront) Request ID: FXbt9EywfEGvdubVlZiFKgTT3YmqEtSrU0yVR32uMrk6iLjPVbPRBA== </PRE> <ADDRESS> </ADDRESS> </BODY></HTML>
Open service 18.173.154.92:80 · api.dev.myqsrsoft.com
2026-01-12 03:48
HTTP/1.1 403 Forbidden Server: CloudFront Date: Mon, 12 Jan 2026 03:48:36 GMT Content-Type: text/html Content-Length: 915 Connection: close X-Cache: Error from cloudfront Via: 1.1 b9c5f3514baef1f70c91fc9b0be37d2e.cloudfront.net (CloudFront) X-Amz-Cf-Pop: MUC50-P3 X-Amz-Cf-Id: txe1SWLc3j4CX21ieyGtnjGQ_0jAsA4PP71KtGMJAfqa9A2ZHJMq-g== Page title: ERROR: The request could not be satisfied <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd"> <HTML><HEAD><META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1"> <TITLE>ERROR: The request could not be satisfied</TITLE> </HEAD><BODY> <H1>403 ERROR</H1> <H2>The request could not be satisfied.</H2> <HR noshade size="1px"> Bad request. We can't connect to the server for this app or website at this time. There might be too much traffic or a configuration error. Try again later, or contact the app or website owner. <BR clear="all"> If you provide content to customers through CloudFront, you can find steps to troubleshoot and help prevent this error by reviewing the CloudFront documentation. <BR clear="all"> <HR noshade size="1px"> <PRE> Generated by cloudfront (CloudFront) Request ID: txe1SWLc3j4CX21ieyGtnjGQ_0jAsA4PP71KtGMJAfqa9A2ZHJMq-g== </PRE> <ADDRESS> </ADDRESS> </BODY></HTML>
Open service 18.173.154.6:80 · api.dev.myqsrsoft.com
2026-01-12 03:48
HTTP/1.1 403 Forbidden Server: CloudFront Date: Mon, 12 Jan 2026 03:48:36 GMT Content-Type: text/html Content-Length: 915 Connection: close X-Cache: Error from cloudfront Via: 1.1 129b4a1f09d5313624ec15fced944d6e.cloudfront.net (CloudFront) X-Amz-Cf-Pop: MUC50-P3 X-Amz-Cf-Id: yd5BEami1ro6D6vICtW1qcRIZkAfj4QHndx8Sx-ufPcmmJi3LgYtSw== Page title: ERROR: The request could not be satisfied <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd"> <HTML><HEAD><META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1"> <TITLE>ERROR: The request could not be satisfied</TITLE> </HEAD><BODY> <H1>403 ERROR</H1> <H2>The request could not be satisfied.</H2> <HR noshade size="1px"> Bad request. We can't connect to the server for this app or website at this time. There might be too much traffic or a configuration error. Try again later, or contact the app or website owner. <BR clear="all"> If you provide content to customers through CloudFront, you can find steps to troubleshoot and help prevent this error by reviewing the CloudFront documentation. <BR clear="all"> <HR noshade size="1px"> <PRE> Generated by cloudfront (CloudFront) Request ID: yd5BEami1ro6D6vICtW1qcRIZkAfj4QHndx8Sx-ufPcmmJi3LgYtSw== </PRE> <ADDRESS> </ADDRESS> </BODY></HTML>
Open service 18.173.154.24:443 · api.dev.myqsrsoft.com
2026-01-12 03:48
HTTP/1.1 403 Forbidden
Content-Type: application/json
Content-Length: 42
Connection: close
Date: Mon, 12 Jan 2026 03:48:37 GMT
X-Amzn-Trace-Id: Root=1-69646f15-6b9b32d271c08af127019eab
x-amzn-RequestId: 03a4e08d-d22c-45e1-9e7f-1c81731afe13
x-amzn-ErrorType: MissingAuthenticationTokenException
x-amz-apigw-id: XDZLaFLaIAMEVSw=
X-Cache: Error from cloudfront
Via: 1.1 66e1af4a9e82225c770ca97b3baaf86e.cloudfront.net (CloudFront)
X-Amz-Cf-Pop: MUC50-P3
X-Amz-Cf-Id: xPatt__yLiYw8b96-fWCq9_hCTIg29dsJ7Zw_HlMLPoPec1q-YWLfw==
{"message":"Missing Authentication Token"}
Open service 18.173.154.8:80 · api.dev.myqsrsoft.com
2026-01-12 03:48
HTTP/1.1 403 Forbidden Server: CloudFront Date: Mon, 12 Jan 2026 03:48:37 GMT Content-Type: text/html Content-Length: 915 Connection: close X-Cache: Error from cloudfront Via: 1.1 bc5539655ffc88be2596a0239ddfae52.cloudfront.net (CloudFront) X-Amz-Cf-Pop: MUC50-P3 X-Amz-Cf-Id: aSn9WO2pLF7Ibtmvi9I9HX4q_JK2t8aeIkQB95mhyJTExNOmLhTVuw== Page title: ERROR: The request could not be satisfied <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd"> <HTML><HEAD><META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1"> <TITLE>ERROR: The request could not be satisfied</TITLE> </HEAD><BODY> <H1>403 ERROR</H1> <H2>The request could not be satisfied.</H2> <HR noshade size="1px"> Bad request. We can't connect to the server for this app or website at this time. There might be too much traffic or a configuration error. Try again later, or contact the app or website owner. <BR clear="all"> If you provide content to customers through CloudFront, you can find steps to troubleshoot and help prevent this error by reviewing the CloudFront documentation. <BR clear="all"> <HR noshade size="1px"> <PRE> Generated by cloudfront (CloudFront) Request ID: aSn9WO2pLF7Ibtmvi9I9HX4q_JK2t8aeIkQB95mhyJTExNOmLhTVuw== </PRE> <ADDRESS> </ADDRESS> </BODY></HTML>
Open service 18.173.154.6:443 · api.dev.myqsrsoft.com
2026-01-12 03:48
HTTP/1.1 403 Forbidden
Content-Type: application/json
Content-Length: 42
Connection: close
Date: Mon, 12 Jan 2026 03:48:36 GMT
X-Amzn-Trace-Id: Root=1-69646f14-5bde996128b7c95c447fb0af
x-amzn-RequestId: 1052e77c-c7e7-4a73-a715-7d31297e2efd
x-amzn-ErrorType: MissingAuthenticationTokenException
x-amz-apigw-id: XDZLRFjGoAMEZew=
X-Cache: Error from cloudfront
Via: 1.1 bc8243121fd94c5b2714caac07caccde.cloudfront.net (CloudFront)
X-Amz-Cf-Pop: MUC50-P3
X-Amz-Cf-Id: DykKYnf7RhmpPdSMQceZptRWQcxe-0xU9tfRGYNgyrFEjcAfrl4jKw==
{"message":"Missing Authentication Token"}
Open service 18.173.154.8:443 · api.dev.myqsrsoft.com
2026-01-12 03:48
HTTP/1.1 403 Forbidden
Content-Type: application/json
Content-Length: 42
Connection: close
Date: Mon, 12 Jan 2026 03:48:36 GMT
X-Amzn-Trace-Id: Root=1-69646f14-19edd64b20cdab613f43f85c
x-amzn-RequestId: 894a05e5-8af3-4561-8220-04a86171115a
x-amzn-ErrorType: MissingAuthenticationTokenException
x-amz-apigw-id: XDZLQGdSoAMEX0w=
X-Cache: Error from cloudfront
Via: 1.1 cb7ecd2473bf95a71af8d1ff8d1034fa.cloudfront.net (CloudFront)
X-Amz-Cf-Pop: MUC50-P3
X-Amz-Cf-Id: zALfRWRr5GYC91n05mNGpQnUMz9q0CtnBJWBKITycxp2O-iOmtx41Q==
{"message":"Missing Authentication Token"}