Hi everyone.
For the last 24 hours I’ve been getting the message “Error while executing the Mesh to MetaHuman service” when trying to complete a new character.
It worked perfectly prior to this.
Is the service down right now?
Is it working properly for anybody today?
BTW, I’m in the UK and on UE 5.02 with the latest MH and Quixel plugins installed.
Thanks, Tammy.
I’m in the UK and getting this error too.
That’s good to know, if you see what I mean.
It will just be a matter of waiting it out then!
I’m in the U.S and have been getting this error too. Others over here have posted the same problem so, I guess it’s a worldwide issue.
Good to know. I’ve been pulling my hair out trying to figure out why my mesh to metahuman isn’t working. Also, when importing my head mesh from Maya/Arnold materials are always white. I have to reassign all the textures on a new material in Unreal 5. Is this normal? Do Arnold materials not go into Unreal?
It’s all working properly now, thanks Epic!
Hi Folks,
I think I figured it out.
If you have Bit Defender installed, you need to disable the firewall
Go to PROTECTION > DISABLE FIREWALL and VIOLA!!
If you don’t have it installed may be try exiting Rivatuner/Afterburner & GForce Experience
Good luck!
have this exact issue as well
LogMetaHumanIdentity: Display: Logged in to Mesh To MetaHuman service
Maintenance finished in +00:00:36.576 and deleted 1062 file(s) with total size 84 MiB.
LogHttp: Warning: 00000BF84A1A6E00: HTTP request timed out after 180.00 seconds URL=https://metahuman-ars.ucs.on.epicgames.com/autorigservice/solve4
LogHttp: Warning: 00000BF84A1A6E00: request failed, libcurl error: 0 (No error)
LogHttp: Warning: 00000BF84A1A6E00: libcurl info message cache 0 (Found bundle for host metahuman-ars.ucs.on.epicgames.com: 0xbf824080090 [can pipeline])
LogHttp: Warning: 00000BF84A1A6E00: libcurl info message cache 1 (Re-using existing connection! (#0) with host metahuman-ars.ucs.on.epicgames.com)
LogHttp: Warning: 00000BF84A1A6E00: libcurl info message cache 2 (Connected to metahuman-ars.ucs.on.epicgames.com (34.237.162.222) port 443 (#0))
LogHttp: Warning: 00000BF84A1A6E00: libcurl info message cache 3 (We are completely uploaded and fine)
LogHttp: Warning: 00000BF84A1A6E00: libcurl info message cache 4 (Closing connection 0)
LogHttp: Warning: 00000BF84A1A6E00: 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’
Pinging the server results in timeouts as well
I meet the same issue. I captured the data by , which showed that the backend didn’t send the response back after the plugin sending the request.
LogMetaHumanIdentity: Display: Logged in to Mesh To MetaHuman service
LogHttp: Warning: 000009C899F87800: HTTP request timed out after 180.00 seconds URL=https://metahuman-ars.ucs.on.epicgames.com/autorigservice/solve4
LogHttp: Warning: 000009C899F87800: request failed, libcurl error: 0 (No error)
LogHttp: Warning: 000009C899F87800: libcurl info message cache 0 (Found bundle for host metahuman-ars.ucs.on.epicgames.com: 0x9c823870d50 [can pipeline])
LogHttp: Warning: 000009C899F87800: libcurl info message cache 1 (Re-using existing connection! (#11) with host metahuman-ars.ucs.on.epicgames.com)
LogHttp: Warning: 000009C899F87800: libcurl info message cache 2 (Connected to metahuman-ars.ucs.on.epicgames.com (34.237.162.222) port 443 (#11))
LogHttp: Warning: 000009C899F87800: libcurl info message cache 3 (We are completely uploaded and fine)
LogHttp: Warning: 000009C899F87800: libcurl info message cache 4 (Closing connection 11)
LogHttp: Warning: 000009C899F87800: 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'
same here since 2 hours From EU. I tried disabling all kind of firewall things and spamming “Mesh to Metahuman Button” but no luck…
Is there any solution to this yet? I closed everything that others mentioned and I’m clicking the button for hours now and still have the same error.
I replayed the rquest by curl. It seems that it sucks in the server.
this is exactly the reason why I stay away from cloud-based solutions…
Hey guys, it works again (finally!!)
It worked suddenly
Same problem, is not working anymore, from yesterday.
Anyone else?
Me too, now in China
I posted another entry with the error and suddenly worked, best timing ever. I have been spamming the button for days lmao
This is happening for me right now too, is the server down?
