[Bug 🐞]: Can't deploy on mainnet

[mik-tf]

What happened?

• Can't deploy on mainnet
• Tried many nodes, node 1, 2016, and others
• Tried Saturday and today Sunday

What did you expect?

• Should be able to deploy full vm with certified or not certified farm

What browsers are you seeing the problem on?

No response

ZOS info

No response

Dashboard info

• example with wireguard + mycelium as networks, certified node, can't remember the node ID

• example with mycelium only as network, node 6656

• example with mycelium and node 1

@xmonader

weblets info

No response

Relevant log output

No response

[ramezsaeed]

just deployed using auto select node and worked fine, both microVM and fullVM

Nodes:

• 5687
• 7031

Also working fine on node 1

But node 6656 is on standby state and failed to get it to start deploy

[mik-tf]

Just tried deploying full vm on 5687 and I get this:

[ramezsaeed]

I suspect something wrong with your twin, maybe you can test with another account.
and provide this twin here in the issue.

Its working for the same node here 5687

[mik-tf]

I could deploy with this same account/twin weeks ago and I had no problem. So this means there is something wrong on the grid side right? We can't tell users to just create a new account (and then go through another KYC process) if there is an issue with the grid. Wdyt?

[ramezsaeed]

yes indeed
I didn't mean you leave your twin and use another one.
I just mean you can test with another twin and send your twin here so Dev team can investigate whats wrong with the failed twin.

[mik-tf]

Gotcha.

My twin ID is: 6905

As for testing with another twin, @scottyeager tried with another twin and it works.

The issue looks very similar to this: threefoldtech/tfgrid-sdk-ts#3477