I've got problem with HTTP responses. They are skipped by the Engine but I can see them in 3rd party packet sniffer.

S_Q_R · March 17, 2023, 11:57am

Hi. Thanks for entering my question . I have problem on one of my PC. So I tried to use VoiceSDK plugin from meta. I’m using sample project with sample app so there is no coding on my side. I got 2 machines with exact same software setup. Both win10 22h2 version. Both UE 4.27. Both got bitdefender antivirus and I turned it off (build in firewall too) in order to make it work but no with no success.
Here is what happens.
On laptop:
I’m seding http request and im getting response - work like expected
On Desktop:
Im sending HTTP request and it’s not getting any reponse. I’m not getting any logs. It’s just stays there forever with status equal to Processing. Its idling even after I close the editor and writting to log this message every 0.5 second
[2023.03.17-11.54.08:929][163]LogHttp: Display: Sleeping 0.500s to wait for 2 outstanding Http requests.

I tried to reinstall engine (i even formatted my pc and made clean windows install)
When i used curl from console i got response immediately so it looks like its not a network issue. I also installed packet sniffer and I’m seeing response. Its just unreal thing that is ignores it and not call proper delegates. Any ideas how to fix that? Thanks!

P.S. It also happens with request to different servers I can see in request that diagnostic to epic games is also processing for eternity (https://datarouter.ol.epicgames.com/datarouter/api/v1/public/data?SessionID…)

High500 · March 17, 2023, 12:48pm

hi @S_Q_R

Have you double checked the firewall on the machine with the issue is allowing the data into the code? You may see a packet on the network but your machine might be blocking it from going where intended.

Might not be the issue just throwing that out there and worth a look no?

S_Q_R · March 17, 2023, 1:50pm

I double checked that.

UE4 got permission in firewall to use both private and public network. And I don’t get responses even when firewall is completely turned off so I think problem lays somewhere else But thanks for suggestion

High500 · March 17, 2023, 2:13pm

worth a try, but that said does that SDK you use register as a seperate dll process which may also need firewall access? best way is to check on the machine you know works.

Sorry if its clutching at straws

S_Q_R · March 17, 2023, 2:34pm

I reseted firewall rules and don’t see anything related to sdk on both machines.
Here is veryverbose LogHttp from pc that doesn’t work

LogHttp: Verbose: 0000021007C46B00: URL='https://api.wit.ai/message?v=20230126&q=cube%20red'

LogHttp: Verbose: 0000021007C46B00: Verb='GET'

LogHttp: Verbose: 0000021007C46B00: Custom headers are present

LogHttp: Verbose: 0000021007C46B00: Payload size=0

LogHttp: Verbose: 0000021007C46B00: request (easy handle:0000021061CB4D40) has been added to threaded queue for processing

LogHttp: Verbose: 0000021007C46B00: Adding header 'User-Agent: wit-unreal-49.0.1,wit-unreal,Windows-10.0.19045.1.256.64bit,Unknown,F61B503547C723EA39E329BB0D061C50,Unknown,Editor,Original'

LogHttp: Verbose: 0000021007C46B00: Adding header 'Content-Length: 0'

LogHttp: Verbose: 0000021007C46B00: Adding header 'Expect: '

LogHttp: 0000021007C46B00: Starting GET request to URL='https://api.wit.ai/message?v=20230126&q=cube%20red'

LogHttp: Verbose: 0000021007C46B00: request (easy handle:0000021061CB4D40) has started threaded processing

LogHttp: VeryVerbose: 0000021007C46B00: ' Trying 31.13.84.56...'

LogHttp: VeryVerbose: 0000021007C46B00: 'TCP_NODELAY set'

LogHttp: VeryVerbose: 0000021007C46B00: 'Connected to api.wit.ai (31.13.84.56) port 443 (#0)'

LogHttp: VeryVerbose: 0000021007C46B00: 'ALPN, offering http/1.1'

LogHttp: VeryVerbose: 0000021007C46B00: 'Cipher selection: ALL:!EXPORT:!EXPORT40:!EXPORT56:!aNULL:!LOW:!RC4:@STRENGTH'

LogHttp: VeryVerbose: 0000021007C46B00: Sent SSL data (5 bytes)

LogHttp: VeryVerbose: 0000021007C46B00: 'TLSv1.3 (OUT), TLS handshake, Client hello (1):'

LogHttp: VeryVerbose: 0000021007C46B00: Sent SSL data (512 bytes)

LogHttp: VeryVerbose: 0000021007C46B00: Received SSL data (5 bytes)

LogHttp: VeryVerbose: 0000021007C46B00: 'TLSv1.3 (IN), TLS handshake, Server hello (2):'

LogHttp: VeryVerbose: 0000021007C46B00: Received SSL data (122 bytes)

LogHttp: VeryVerbose: 0000021007C46B00: Received SSL data (5 bytes)

LogHttp: VeryVerbose: 0000021007C46B00: Received SSL data (5 bytes)

LogHttp: VeryVerbose: 0000021007C46B00: 'TLSv1.3 (IN), TLS Unknown, Certificate Status (22):'

LogHttp: VeryVerbose: 0000021007C46B00: Received SSL data (1 bytes)

LogHttp: VeryVerbose: 0000021007C46B00: 'TLSv1.3 (IN), TLS handshake, Unknown (8):'

LogHttp: VeryVerbose: 0000021007C46B00: Received SSL data (21 bytes)

LogHttp: VeryVerbose: 0000021007C46B00: Received SSL data (5 bytes)

LogHttp: VeryVerbose: 0000021007C46B00: 'TLSv1.3 (IN), TLS Unknown, Certificate Status (22):'

LogHttp: VeryVerbose: 0000021007C46B00: Received SSL data (1 bytes)

LogHttp: VeryVerbose: 0000021007C46B00: Received SSL data (5 bytes)

LogHttp: VeryVerbose: 0000021007C46B00: 'TLSv1.3 (IN), TLS Unknown, Certificate Status (22):'

LogHttp: VeryVerbose: 0000021007C46B00: Received SSL data (1 bytes)

LogHttp: VeryVerbose: 0000021007C46B00: 'TLSv1.3 (IN), TLS handshake, Certificate (11):'

LogHttp: VeryVerbose: 0000021007C46B00: Received SSL data (2954 bytes)

LogHttp: VeryVerbose: 0000021007C46B00: 'TLSv1.3 (IN), TLS handshake, CERT verify (15):'

LogHttp: VeryVerbose: 0000021007C46B00: Received SSL data (264 bytes)

LogHttp: VeryVerbose: 0000021007C46B00: 'TLSv1.3 (IN), TLS handshake, Finished (20):'

LogHttp: VeryVerbose: 0000021007C46B00: Received SSL data (36 bytes)

LogHttp: VeryVerbose: 0000021007C46B00: Sent SSL data (5 bytes)

LogHttp: VeryVerbose: 0000021007C46B00: 'TLSv1.3 (OUT), TLS change cipher, Client hello (1):'

LogHttp: VeryVerbose: 0000021007C46B00: Sent SSL data (1 bytes)

LogHttp: VeryVerbose: 0000021007C46B00: Sent SSL data (5 bytes)

LogHttp: VeryVerbose: 0000021007C46B00: 'TLSv1.3 (OUT), TLS Unknown, Certificate Status (22):'

LogHttp: VeryVerbose: 0000021007C46B00: Sent SSL data (1 bytes)

LogHttp: VeryVerbose: 0000021007C46B00: 'TLSv1.3 (OUT), TLS handshake, Finished (20):'

LogHttp: VeryVerbose: 0000021007C46B00: Sent SSL data (36 bytes)

LogHttp: VeryVerbose: 0000021007C46B00: 'SSL connection using TLSv1.3 / TLS_CHACHA20_POLY1305_SHA256'

LogHttp: VeryVerbose: 0000021007C46B00: 'ALPN, server accepted to use http/1.1'

LogHttp: VeryVerbose: 0000021007C46B00: 'Server certificate:'

LogHttp: VeryVerbose: 0000021007C46B00: ' subject: C=US; ST=California; L=Menlo Park; O=Meta Platforms, Inc.; CN=*.wit.ai'

LogHttp: VeryVerbose: 0000021007C46B00: ' start date: Jan 8 00:00:00 2023 GMT'

LogHttp: VeryVerbose: 0000021007C46B00: ' expire date: Mar 24 23:59:59 2023 GMT'

LogHttp: VeryVerbose: 0000021007C46B00: ' subjectAltName: host "api.wit.ai" matched cert's "*.wit.ai"'

LogHttp: VeryVerbose: 0000021007C46B00: ' issuer: C=US; O=DigiCert Inc; OU=www.digicert.com; CN=DigiCert SHA2 High Assurance Server CA'

LogHttp: VeryVerbose: 0000021007C46B00: ' SSL certificate verify ok.'

LogHttp: VeryVerbose: 0000021007C46B00: Sent SSL data (5 bytes)

LogHttp: VeryVerbose: 0000021007C46B00: 'TLSv1.3 (OUT), TLS Unknown, Unknown (23):'

LogHttp: VeryVerbose: 0000021007C46B00: Sent SSL data (1 bytes)

LogHttp: VeryVerbose: 0000021007C46B00: Sent header (321 bytes) - GET /message?v=20230126&q=cube%20red HTTP/1.1Host: api.wit.aiAccept: */*Accept-Encoding: deflate, gzipAuthorization: Bearer SACKYPLWQTXOOMYSSXMSHJV7EAQYCJTXUser-Agent: wit-unreal-49.0.1,wit-unreal,Windows-10.0.19045.1.256.64bit,Unknown,F61B503547C723EA39E329BB0D061C50,Unknown,Editor,OriginalCo

and here is log from pc that works

LogHttp: Verbose: 0000024F0F33A400: URL='https://api.wit.ai/message?v=20230126&q=cube%20red'

LogHttp: Verbose: 0000024F0F33A400: Verb='GET'

LogHttp: Verbose: 0000024F0F33A400: Custom headers are present

LogHttp: Verbose: 0000024F0F33A400: Payload size=0

LogHttp: Verbose: 0000024F0F33A400: request (easy handle:0000024F4D3646C0) has been added to threaded queue for processing

LogHttp: Verbose: 0000024F0F33A400: Adding header 'User-Agent: wit-unreal-49.0.1,wit-unreal,Windows-10.0.19045.1.256.64bit,Unknown,F7D68EA4455D05A1BF5426BBE318A367,Unknown,Editor,Original'

LogHttp: Verbose: 0000024F0F33A400: Adding header 'Content-Length: 0'

LogHttp: Verbose: 0000024F0F33A400: Adding header 'Expect: '

LogHttp: 0000024F0F33A400: Starting GET request to URL='https://api.wit.ai/message?v=20230126&q=cube%20red'

LogHttp: Verbose: 0000024F0F33A400: request (easy handle:0000024F4D3646C0) has started threaded processing

LogHttp: VeryVerbose: 0000024F0F33A400: 'Connection 1 seems to be dead!'

LogHttp: VeryVerbose: 0000024F0F33A400: 'Closing connection 1'

LogHttp: VeryVerbose: 0000024F0F33A400: Sent SSL data (5 bytes)

LogHttp: VeryVerbose: 0000024F0F33A400: 'TLSv1.3 (OUT), TLS Unknown, Unknown (21):'

LogHttp: VeryVerbose: 0000024F0F33A400: Sent SSL data (1 bytes)

LogHttp: VeryVerbose: 0000024F0F33A400: 'TLSv1.3 (OUT), TLS alert, Client hello (1):'

LogHttp: VeryVerbose: 0000024F0F33A400: Sent SSL data (2 bytes)

LogHttp: VeryVerbose: 0000024F0F33A400: ' Trying 31.13.84.56...'

LogHttp: VeryVerbose: 0000024F0F33A400: 'TCP_NODELAY set'

LogHttp: VeryVerbose: 0000024F0F33A400: 'Connected to api.wit.ai (31.13.84.56) port 443 (#2)'

LogHttp: VeryVerbose: 0000024F0F33A400: 'ALPN, offering http/1.1'

LogHttp: VeryVerbose: 0000024F0F33A400: 'Cipher selection: ALL:!EXPORT:!EXPORT40:!EXPORT56:!aNULL:!LOW:!RC4:@STRENGTH'

LogHttp: VeryVerbose: 0000024F0F33A400: 'SSL re-using session ID'

LogHttp: VeryVerbose: 0000024F0F33A400: Sent SSL data (5 bytes)

LogHttp: VeryVerbose: 0000024F0F33A400: 'TLSv1.3 (OUT), TLS handshake, Client hello (1):'

LogHttp: VeryVerbose: 0000024F0F33A400: Sent SSL data (512 bytes)

LogHttp: VeryVerbose: 0000024F0F33A400: Received SSL data (5 bytes)

LogHttp: VeryVerbose: 0000024F0F33A400: 'TLSv1.3 (IN), TLS handshake, Server hello (2):'

LogHttp: VeryVerbose: 0000024F0F33A400: Received SSL data (122 bytes)

LogHttp: VeryVerbose: 0000024F0F33A400: Received SSL data (5 bytes)

LogHttp: VeryVerbose: 0000024F0F33A400: Received SSL data (5 bytes)

LogHttp: VeryVerbose: 0000024F0F33A400: 'TLSv1.3 (IN), TLS Unknown, Certificate Status (22):'

LogHttp: VeryVerbose: 0000024F0F33A400: Received SSL data (1 bytes)

LogHttp: VeryVerbose: 0000024F0F33A400: 'TLSv1.3 (IN), TLS handshake, Unknown (8):'

LogHttp: VeryVerbose: 0000024F0F33A400: Received SSL data (21 bytes)

LogHttp: VeryVerbose: 0000024F0F33A400: Received SSL data (5 bytes)

LogHttp: VeryVerbose: 0000024F0F33A400: 'TLSv1.3 (IN), TLS Unknown, Certificate Status (22):'

LogHttp: VeryVerbose: 0000024F0F33A400: Received SSL data (1 bytes)

LogHttp: VeryVerbose: 0000024F0F33A400: Received SSL data (5 bytes)

LogHttp: VeryVerbose: 0000024F0F33A400: 'TLSv1.3 (IN), TLS Unknown, Certificate Status (22):'

LogHttp: VeryVerbose: 0000024F0F33A400: Received SSL data (1 bytes)

LogHttp: VeryVerbose: 0000024F0F33A400: 'TLSv1.3 (IN), TLS handshake, Certificate (11):'

LogHttp: VeryVerbose: 0000024F0F33A400: Received SSL data (2954 bytes)

LogHttp: VeryVerbose: 0000024F0F33A400: 'TLSv1.3 (IN), TLS handshake, CERT verify (15):'

LogHttp: VeryVerbose: 0000024F0F33A400: Received SSL data (264 bytes)

LogHttp: VeryVerbose: 0000024F0F33A400: 'TLSv1.3 (IN), TLS handshake, Finished (20):'

LogHttp: VeryVerbose: 0000024F0F33A400: Received SSL data (36 bytes)

LogHttp: VeryVerbose: 0000024F0F33A400: Sent SSL data (5 bytes)

LogHttp: VeryVerbose: 0000024F0F33A400: 'TLSv1.3 (OUT), TLS change cipher, Client hello (1):'

LogHttp: VeryVerbose: 0000024F0F33A400: Sent SSL data (1 bytes)

LogHttp: VeryVerbose: 0000024F0F33A400: Sent SSL data (5 bytes)

LogHttp: VeryVerbose: 0000024F0F33A400: 'TLSv1.3 (OUT), TLS Unknown, Certificate Status (22):'

LogHttp: VeryVerbose: 0000024F0F33A400: Sent SSL data (1 bytes)

LogHttp: VeryVerbose: 0000024F0F33A400: 'TLSv1.3 (OUT), TLS handshake, Finished (20):'

LogHttp: VeryVerbose: 0000024F0F33A400: Sent SSL data (36 bytes)

LogHttp: VeryVerbose: 0000024F0F33A400: 'SSL connection using TLSv1.3 / TLS_CHACHA20_POLY1305_SHA256'

LogHttp: VeryVerbose: 0000024F0F33A400: 'ALPN, server accepted to use http/1.1'

LogHttp: VeryVerbose: 0000024F0F33A400: 'old SSL session ID is stale, removing'

LogHttp: VeryVerbose: 0000024F0F33A400: 'Server certificate:'

LogHttp: VeryVerbose: 0000024F0F33A400: ' subject: C=US; ST=California; L=Menlo Park; O=Meta Platforms, Inc.; CN=*.wit.ai'

LogHttp: VeryVerbose: 0000024F0F33A400: ' start date: Jan 8 00:00:00 2023 GMT'

LogHttp: VeryVerbose: 0000024F0F33A400: ' expire date: Mar 24 23:59:59 2023 GMT'

LogHttp: VeryVerbose: 0000024F0F33A400: ' subjectAltName: host "api.wit.ai" matched cert's "*.wit.ai"'

LogHttp: VeryVerbose: 0000024F0F33A400: ' issuer: C=US; O=DigiCert Inc; OU=www.digicert.com; CN=DigiCert SHA2 High Assurance Server CA'

LogHttp: VeryVerbose: 0000024F0F33A400: ' SSL certificate verify ok.'

LogHttp: VeryVerbose: 0000024F0F33A400: Sent SSL data (5 bytes)

LogHttp: VeryVerbose: 0000024F0F33A400: 'TLSv1.3 (OUT), TLS Unknown, Unknown (23):'

LogHttp: VeryVerbose: 0000024F0F33A400: Sent SSL data (1 bytes)

LogHttp: VeryVerbose: 0000024F0F33A400: Sent header (321 bytes) - GET /message?v=20230126&q=cube%20red HTTP/1.1Host: api.wit.aiAccept: */*Accept-Encoding: deflate, gzipAuthorization: Bearer SACKYPLWQTXOOMYSSXMSHJV7EAQYCJTXUser-Agent: wit-unreal-49.0.1,wit-unreal,Windows-10.0.19045.1.256.64bit,Unknown,F7D68EA4455D05A1BF5426BBE318A367,Unknown,Editor,OriginalCo

LogHttp: VeryVerbose: 0000021007C46B00: Sent header (321 bytes) - GET /message?v=20230126&q=cube%20red HTTP/1.1Host: api.wit.aiAccept: */*Accept-Encoding: deflate, gzipAuthorization: Bearer SACKYPLWQTXOOMYSSXMSHJV7EAQYCJTXUser-Agent: wit-unreal-49.0.1,wit-unreal,Windows-10.0.19045.1.256.64bit,Unknown,F61B503547C723EA39E329BB0D061C50,Unknown,Editor,OriginalCo

LogHttp: VeryVerbose: 0000024F0F33A400: Received SSL data (5 bytes)

LogHttp: VeryVerbose: 0000024F0F33A400: 'TLSv1.3 (IN), TLS Unknown, Certificate Status (22):'

LogHttp: VeryVerbose: 0000024F0F33A400: Received SSL data (1 bytes)

LogHttp: VeryVerbose: 0000024F0F33A400: 'TLSv1.3 (IN), TLS handshake, Newsession Ticket (4):'

LogHttp: VeryVerbose: 0000024F0F33A400: Received SSL data (149 bytes)

LogHttp: VeryVerbose: 0000024F0F33A400: Received SSL data (5 bytes)

LogHttp: VeryVerbose: 0000024F0F33A400: 'TLSv1.3 (IN), TLS Unknown, Unknown (23):'

LogHttp: VeryVerbose: 0000024F0F33A400: Received SSL data (1 bytes)

LogHttp: VeryVerbose: 0000024F0F33A400: Received header (17 bytes)

LogHttp: Verbose: 0000024F0F33A400: Received response header 'HTTP/1.1 200 OK'.

LogHttp: VeryVerbose: 0000024F0F33A400: Received header (32 bytes)

LogHttp: Verbose: 0000024F0F33A400: Received response header 'Content-Type: application/json'.

LogHttp: VeryVerbose: 0000024F0F33A400: Received header (32 bytes)

LogHttp: Verbose: 0000024F0F33A400: Received response header 'Access-Control-Allow-Origin: *'.

LogHttp: VeryVerbose: 0000024F0F33A400: Received header (33 bytes)

LogHttp: Verbose: 0000024F0F33A400: Received response header 'Access-Control-Allow-Headers: *'.

LogHttp: VeryVerbose: 0000024F0F33A400: Received header (37 bytes)

LogHttp: Verbose: 0000024F0F33A400: Received response header 'Date: Fri, 17 Mar 2023 14:05:32 GMT'.

LogHttp: VeryVerbose: 0000024F0F33A400: Received header (24 bytes)

LogHttp: Verbose: 0000024F0F33A400: Received response header 'Connection: keep-alive'.

LogHttp: VeryVerbose: 0000024F0F33A400: Received header (21 bytes)

LogHttp: Verbose: 0000024F0F33A400: Received response header 'Content-Length: 771'.

LogHttp: Verbose: 0000024F0F33A400: Received response header ''.

LogHttp: VeryVerbose: 0000024F0F33A400: Received header (2 bytes)

LogHttp: VeryVerbose: 0000024F0F33A400: Received data (1 bytes)

LogHttp: Verbose: 0000024F0F33A400: ReceiveResponseBodyCallback: 1 bytes out of 771 received. (SizeInBlocks=1, BlockSizeInBytes=1, Response->TotalBytesRead=0, Response->GetContentLength()=771, SizeToDownload=1 (<-this will get returned from the callback))

LogHttp: VeryVerbose: 0000024F0F33A400: Received SSL data (5 bytes)

LogHttp: VeryVerbose: 0000024F0F33A400: 'TLSv1.3 (IN), TLS Unknown, Unknown (23):'

LogHttp: VeryVerbose: 0000024F0F33A400: Received SSL data (1 bytes)

LogHttp: VeryVerbose: 0000024F0F33A400: Received data (770 bytes)

LogHttp: Verbose: 0000024F0F33A400: ReceiveResponseBodyCallback: 771 bytes out of 771 received. (SizeInBlocks=1, BlockSizeInBytes=770, Response->TotalBytesRead=1, Response->GetContentLength()=771, SizeToDownload=770 (<-this will get returned from the callback))

LogHttp: VeryVerbose: 0000024F0F33A400: 'Connection #2 to host api.wit.ai left intact'

LogHttp: Verbose: Request 0000024F0F33A400 (easy handle:0000024F4D3646C0) has completed (code:0) and has been marked as such

LogHttp: 0000024F0F33A400: request has been successfully processed. URL: https://api.wit.ai/message?v=20230126&q=cube%20red, HTTP code: 200, content length: 771, actual payload size: 771, elapsed: 0.61s

LogHttp: Verbose: 0000024F0F33A400 Response Header Content-Type: application/json

LogHttp: Verbose: 0000024F0F33A400 Response Header Access-Control-Allow-Origin: *

LogHttp: Verbose: 0000024F0F33A400 Response Header Access-Control-Allow-Headers: *

LogHttp: Verbose: 0000024F0F33A400 Response Header Date: Fri, 17 Mar 2023 14:05:32 GMT

LogHttp: Verbose: 0000024F0F33A400 Response Header Connection: keep-alive

LogHttp: Verbose: 0000024F0F33A400 Response Header Content-Length: 771

High500 · March 17, 2023, 4:14pm

you first log ends earlier than the second.

A few points, do you require seperate API keys per user/connection? or are keys not used

2nd have you looked at the sample project?

https://redirect.epicgames.com/?redirectTo=https://github.com/wit-ai/voicesdk-unreal-samples/blob/main/Marketplace_README.md

S_Q_R · March 17, 2023, 7:46pm

Thanks for reply.
Log ends earlier but I pasted all I got. Request is being send but left with no response. I stopped using SDK to eliminate as much of code I can and wrote this snippet.

void AMyDummyActor::SendHTTPRequest()
{
	FHttpModule& HttpModule = FHttpModule::Get();
	TSharedRef<IHttpRequest, ESPMode::ThreadSafe> HttpRequest = HttpModule.CreateRequest();
	HttpRequest->SetURL(TEXT("https://api.wit.ai/message?v=20230126&q=cube%20red"));
	HttpRequest->SetVerb(TEXT("GET"));
	HttpRequest->SetHeader("Authorization", "Bearer SACKYPLWQTXOOMYSSXMSHJV7EAQYCJTX");
	HttpRequest->SetHeader("User-Agent", "wit-unreal-49.0.1,wit-unreal,Windows-10.0.19045.1.256.64bit,Unknown,7CC43373498248355931D2878EA829FC,Unknown,Editor,Original");
	HttpRequest->OnProcessRequestComplete().BindLambda([](FHttpRequestPtr Request, FHttpResponsePtr Response, bool bSuccess)
		{
			if (bSuccess)
			{
				UE_LOG(LogTemp, Warning, TEXT("HTTP request succeeded:"));// % s"), *Response->GetContentAsString());
			}
			else
			{
				UE_LOG(LogTemp, Error, TEXT("HTTP request failed: "));//%s"), *Response->GetContentAsString());
			}
		});
	if (!HttpRequest->ProcessRequest())
	{
		GEngine->AddOnScreenDebugMessage(1, 600.0f, FColor::Green, TEXT("Request failed at start!"));
	}
}

Just to send some simple request. It works well on other machine but no luck on this one.
I’m getting out of ideas

P.S. and yes I saw this sample projects. Its the one i’m trying to run.

S_Q_R · March 18, 2023, 3:25pm

I installed fiddler everywhere and not I’m getting response but only when I use Fiddler. So when traffic goes through fiddler its ok. Anyone know why it might occur?

High500 · March 18, 2023, 4:58pm

As you sent a simple request and that doesnt work then for sure it sounds like a computer issue not an sdk issue as either the request isnt getting to the server which is an outgoing rule issue, or the reply isnt coming back. This could also be your router misrouting the requests back. Can you sniff any response at all that matches the reply you should be getting but do it local network wide incase uPnP is not quite doing its job correctly

Also maybe completley disable the firewall on the problem machine just until you finish testing. , make sure all AV is off, make sure you dont have a rogue install of an old firewall and/or antivirus software left installed somewhere

High500 · March 18, 2023, 5:05pm

If i remember right isbt there an app called postman for testing this sort of stuff?

S_Q_R · March 19, 2023, 3:53pm

Thanks for replies. I tried to uninstall AV and turnning of firewall but it didn’t help. Server sees the request send from the engine to its only problem with getting response. I found this and this thread but suggested fix does not work :(. That sounds very simmilar to my case but suggested fix does not work. I tested out builds made with malfunction PC on a PC that gets request properly and they worked. So I’m able to do working build and run in on different PC but not on the one with the problem. But I’m not able to make it work other way around (build from good PC does not work on bad PC) So now I’m not sure where lays the problem. I can send curl request from cmd and I’m getting proper response. UE4 also uses curl but when its called by the engine it does not work. On the other hand it packaged good build so it looks like all setup related to engine is fine. Have no idea whats happening.

S_Q_R · March 21, 2023, 7:32am

So I’ve found yet another forum entry that solved my issue. For anyone having simmilar issue here is the link