Mine exported at 3:30am PDT. I did nothing different than I had been doing all day previously. Maybe I have to switch to swing shift from now on to export custom MHs with “mesh to MH”.
Suddenly it worked
1 Like
Suddenly 
I just cant get this to work, all i get is error message.
Is it not working again now? I’ve been trying for the last few hours and the same error still keeps on showing up
Is anyone else currently getting this problem ? Because mine has been getting the error all night, until now. Still can’t export it.
1 Like
Getting this error today, was there any fix for it? tried like 20 times by now
Me too；Today 2022.10.8。 tried about 30 times now
1 Like
Got the same issue, ■■■■ I was excited to finally try this out today 
1 Like
Maybe because everybody is downloading UE5.1 now? 
getting the same error all of today also. I tried disabling firewall and following any of the other troubleshooting steps mentioned, but so far nothing…
2 Likes
I got this error today. I used mesh to MH 3 days ago all things were ok
2 Likes
Still not working
4 Likes
Any update from anyone ? Still getting the error.
3 Likes
Same error: Error while executing the Mesh to MetaHuman service
Here the full login case it can help someone…
LogHttp: Warning: 0000065710759600: HTTP request timed out after 180.00 seconds URL=cant place more then 2 url
LogHttp: Warning: 0000065710759600: request failed, libcurl error: 0 (No error)
LogHttp: Warning: 0000065710759600: libcurl info message cache 0 (Found bundle for host cant place more then 2 url: 0x656a28d0de0 [can pipeline])
LogHttp: Warning: 0000065710759600: libcurl info message cache 1 (Re-using existing connection! (#10) with host metahuman-ars.ucs.on.epicgames.com)
LogHttp: Warning: 0000065710759600: libcurl info message cache 2 (Connected to metahuman-ars.ucs.on.epicgames.com (34.237.158.253) port 443 (#10))
LogHttp: Warning: 0000065710759600: libcurl info message cache 3 (We are completely uploaded and fine)
LogHttp: Warning: 0000065710759600: libcurl info message cache 4 (Closing connection 10)
LogHttp: Warning: 0000065710759600: libcurl info message cache 5 (TLSv1.2 (OUT), TLS alert, Client hello (1)
LogSlate: Window ‘Mesh to MetaHuman Error’ being destroyed
Message dialog closed, result: Ok, title: Mesh to MetaHuman Error, text: Error while executing the Mesh to MetaHuman service
LogMetaHumanIdentity: Error: Autorigging service returned an error: ‘Error while executing the Mesh to MetaHuman service’
3 Likes
I keep getting this error as well. Any other tips to get it to work?
5 Likes
Also having the same problem. Tried two different meshes now. Probably 10 attempts.
3 Likes
should I be using 5.1?
same Here 2 day trying
LogMetaHumanIdentity: Error: Autorigging service returned an error: ‘Error while executing the Mesh to MetaHuman service’
LogHttp: Warning: 00000B1A6079D200: HTTP request timed out after 180.00 seconds URL=https://metahuman-ars.ucs.on.epicgames.com/autorigservice/solve4
LogHttp: Warning: 00000B1A6079D200: request failed, libcurl error: 0 (No error)
LogHttp: Warning: 00000B1A6079D200: libcurl info message cache 0 (Found bundle for host metahuman-ars.ucs.on.epicgames.com: 0xb1a268e0300 [can pipeline])
LogHttp: Warning: 00000B1A6079D200: libcurl info message cache 1 (Re-using existing connection! (#3) with host metahuman-ars.ucs.on.epicgames.com)
LogHttp: Warning: 00000B1A6079D200: libcurl info message cache 2 (Connected to metahuman-ars.ucs.on.epicgames.com (54.173.113.89) port 443 (#3))
LogHttp: Warning: 00000B1A6079D200: libcurl info message cache 3 (We are completely uploaded and fine)
LogHttp: Warning: 00000B1A6079D200: libcurl info message cache 4 (Closing connection 3)
LogHttp: Warning: 00000B1A6079D200: libcurl info message cache 5 (TLSv1.2 (OUT), TLS alert, Client hello (1)
LogSlate: Window ‘Mesh to MetaHuman Error’ being destroyed
Message dialog closed, result: Ok, title: Mesh to MetaHuman Error, text: Error while executing the Mesh to MetaHuman service
LogMetaHumanIdentity: Error: Autorigging service returned an error: ‘Error while executing the Mesh to MetaHuman service’
LogViewport: Scene viewport resized to 1522x1234, mode Windowed.
2 Likes
Having the same error since yesterday, could be a server problem?
1 Like