antminer E3 not connecting

I cannot get my antminer e3 to connect. did anyone have any luck?

i notice that the e3 adds stuff to the user name
[Archived image unavailable: https://ibb.co/nL8ikK]

unlike other antminer which just show the user name
[Archived image unavailable: https://ibb.co/jA9Zsz]

I have tried several ways, using proxy, using a=ethash on 3333 or proxy, also tried direct port 3339 and all report pool dead on e3 interface? I've tried going through MRR and then to prohash and still cannot connect? Any update on this?

davidc14 wrote:I have tried several ways, using proxy, using a=ethash on 3333 or proxy, also tried direct port 3339 and all report pool dead on e3 interface? I've tried going through MRR and then to prohash and still cannot connect? Any update on this?

We released a fix earlier this morning for this problem. Try again now, and see if you have any success.

If not, could you attach the images? Above, the post just states "image."

Ok will try when I get back to datacenter, can you tell me if I need to do anything special in username or password fields?

Not connecting either way have tried the following
stratum+tcp://prohashing:3333
[username].worker
a=ethash

stratum+tcp://prohashing:3339
[username].worker
{no password}

stratum+tcp://prohashing:3339
[username]
worker

and proxy:443 with same settings, for all still shows dead in miner?

More information about this issue is now available at https://forums.prohashing.com/viewtopic.php?f=4&t=5933.

any new developments on E3 support?

after using the usual parameters, E3 is shown alive at poolside but no hash accepted and the E3 is not hashing as well.

citronick wrote:any new developments on E3 support?

after using the usual parameters, E3 is shown alive at poolside but no hash accepted and the E3 is not hashing as well.

Could you submit a support tickets with screenshots of the E3 dashboard? Vance is not able to reproduce this issue. He used an E3 for testing.

I think that the difference might be the password arguments or port you're using. The fields we need are requested in the ticket system, so once we get those, we'll see if we forgot to test a configuration you're using.