Please consult the Troubleshooting Node Deployment Errors wiki page, particularly the General Troubleshooting Steps.

If that does not solve your issue, please provide the Support request information requirements and we will assist you further.

In reply to @andrewbattat:matrix.org

Please consult the Troubleshooting Node Deployment Errors wiki page, particularly the General Troubleshooting Steps.

If that does not solve your issue, please provide the Support request information requirements and we will assist you further.

• I'm doing everything right, this is not the first node I've installed and everything has been fine
• I have provided the screenshot above, I get the node number but it does not get registered
• node registration
• Current (Gen-2) Node Deployment Guide (without an HSM)
• not
• not
• not
• The problem is that on any version I get an id number but registration does not happen, my node was degroid for a long time after the error with the update, you said you would prepare a usb drive for recovery, but you did not provide it for a long time and I decided to reinstall, many wrote that this solves the problem.
• Supermicro 1124US-TNRP
  2 x AMD EPYC 7313 (3.00 GHz, 16 cores, 128 MB)
  16 x 32 GB ECC Reg DDR4 3200 RAM
  5 x KCD61VUL6T40
  1 Trusted Platform Module 2.0
• LIM DC
• not
• I don't know what to say.
• I don't know what to say.

Hello everyone!

I have created a dedicated "Space" in Matrix/Element to consolidate all Internet Computer discussion rooms. This will make it easier to locate relevant rooms and people. Please join the Space using the following link: Join the Space

To enhance organization and communication based on earlier feedback, I have also created a separate channel for each node provider with at least one node registered on the IC (as per public dashboard). Each room name follows the format: ic-node-provider-<first-5-chars-of-node-provider-id>.
Below is the complete list of rooms along with their respective node providers. Please join the relevant room for you, and ensure you add an email address in your Element profile settings and enable email notifications. Messages will only be sent when something relevant to your node provider arises, and timely action on your part would be greatly appreciated.

room: ic-node-provider-rbn2y NP: "IC Node Provider Allusion | an1 br1 br2"
room: ic-node-provider-6r5lw NP: "IC Node Provider Sygnum Bank | zh5 zh6 zh7"
room: ic-node-provider-7at4h NP: "IC Node Provider Blockchain Development Labs | bc1 to1 to2"
room: ic-node-provider-bvcsg NP: "IC Node Provider DFINITY Operations SA | mr1 zh2 sh1"
room: ic-node-provider-sixix NP: "IC Node Provider Starbase | ty1 ty2 ty3"
room: ic-node-provider-wwdbq NP: "IC Node Provider Giant Leaf, LLC | at2 mm1 or1 tp1"
room: ic-node-provider-spp3m NP: "IC Node Provider 9Yards Capital | jv1 ch2 ny1"
room: ic-node-provider-6nbcy NP: "IC Node Provider OneSixtyTwo Digital Capital | sg1 sg2 sg3"
room: ic-node-provider-izmhk NP: "IC Node Provider MI Servers | ph1 ch3 st1"
room: ic-node-provider-wdjjk NP: "IC Node Provider Fractal Labs AG | lj1 mb1"
room: ic-node-provider-eipr5 NP: "IC Node Provider 87m Neuron, LLC | pl1 dl1 lv1"
room: ic-node-provider-7ryes NP: "IC Node Provider Archery Blockchain SCSp | ge1 ge2"
room: ic-node-provider-ucjqj NP: "IC Node Provider Tomahawk.vc | zh3 zh4"
room: ic-node-provider-r3yjn NP: "IC Node Provider Pindar Technology Limited | hk1 kr1"
room: ic-node-provider-lq5ra NP: "IC Node Provider DFINITY USA Research LLC | bo1"
room: ic-node-provider-wdnqm NP: "IC Node Provider Virtual Hive Ltd | fr2"
room: ic-node-provider-7a4u2 NP: "IC Node Provider Bigger Capital | aw1"
room: ic-node-provider-ks7ow NP: "IC Node Provider BlockTech Ventures, LLC | sj2"
room: ic-node-provider-vegae NP: "IC Node Provider George Bassadone | vl2 tb1"
room: ic-node-provider-i7dto NP: "IC Node Provider Iancu Aurel | bu1"
room: ic-node-provider-4dibr NP: "IC Node Provider Neptune Partners | sl1"
room: ic-node-provider-sma3p NP: "IC Node Provider BLP22, LLC | at1 at2"
room: ic-node-provider-ihbuj NP: "IC Node Provider Icaria Systems Pty Ltd | mn2"
room: ic-node-provider-unqqg NP: "IC Node Provider Karel Frank | jb1 jb2 sc1"
room: ic-node-provider-64xe5 NP: "IC Node Provider Web3game | hk4 kr2"
room: ic-node-provider-kos24 NP: "IC Node Provider Anonstake | lj2 zg1"
room: ic-node-provider-6sq7t NP: "IC Node Provider GeoNodes LLC | tv1 cr1"
room: ic-node-provider-zy4m7 NP: "IC Node Provider Krishna Enterprises | pl2"
room: ic-node-provider-7uioy NP: "IC Node Provider Marvelous Web3 | nd1 mtl1"
room: ic-node-provider-sqhxa NP: "IC Node Provider 43rd Big Idea Films | hu1"
room: ic-node-provider-ulyfm NP: "IC Node Provider Rivram Inc | nm1"
room: ic-node-provider-nmdd6 NP: "IC Node Provider Honeycomb Capital (Pty) Ltd | jb2"
room: ic-node-provider-cp5ib NP: "IC Node Provider ACCUSET SOLUTIONS | gn1"
room: ic-node-provider-fwnmn NP: "IC Node Provider ANYPOINT PTY LTD | sc1"
room: ic-node-provider-4jjya NP: "IC Node Provider MB Patrankos šūvis | bt1 rg1"
room: ic-node-provider-g2ax6 NP: "IC Node Provider Wancloud limited | hk1"
room: ic-node-provider-qsdw4 NP: "IC Node Provider Carbon Twelve | pr1 es1 "
room: ic-node-provider-diyay NP: "IC Node Provider Artem Horodyskyi | pa2 ma1 rg3 bt1 wa3 li1 ta2"
room: ic-node-provider-dhywe NP: "IC Node Provider Bohatyrov Volodymyr | rg3 ta1 ba1 bn1 wa2 ma1 si1"
room: ic-node-provider-qdj4d NP: "IC Node Provider Boolean Bit, LLC | fm1"
room: ic-node-provider-p6fou NP: "IC Node Provider Goat, LLC | at1"
room: ic-node-provider-ivf2y NP: "IC Node Provider Ivanov Oleksandr | ta2 bt1 wa3 rg1 li1 pa1 ma1"
room: ic-node-provider-dzxyh NP: "IC Node Provider Jimmy Quach | at1"
room: ic-node-provider-4r6qy NP: "IC Node Provider Maksym Ishchenko | ma3 ba1 wa1 rg1 bt1 ta1 bn1"
room: ic-node-provider-cgmhq NP: "IC Node Provider Origin Game | hk4"
room: ic-node-provider-6tg64 NP: "IC Node Provider Rishi Sachdev | tp1"
room: ic-node-provider-3oqw6 NP: "IC Node Provider Vladyslav Popov | pa2 si1 li1 ta2 ma3 wa3 rg1"
room: ic-node-provider-eybf4 NP: "IC Node Provider Geodd Pvt Ltd | cm1"
room: ic-node-provider-optdi NP: "IC Node Provider Illusions In Art (Pty) Ltd | ct1"
room: ic-node-provider-py2kr NP: "IC Node Provider Kontrapunt (Pty) Ltd | ct2"
room: ic-node-provider-efem5 NP: "IC Node Provider Lukas Helebrandt | bn1"
room: ic-node-provider-egb3e NP: "IC Node Provider Richard Ma | tp1"
room: ic-node-provider-a24zv NP: "IC Node Provider Shelburne Ventures, LLC | sj1"
room: ic-node-provider-mme7u NP: "IC Node Provider Wolkboer (Pty) Ltd | jb3"
room: ic-node-provider-7k7b7 NP: "IC Node Provider 1G | fm1"
room: ic-node-provider-ou3o7 NP: "IC Node Provider Mostly Wholesome, Inc. | fm1"
room: ic-node-provider-4fedi NP: "IC Node Provider Power Meta Corporation | hk3"
room: ic-node-provider-eatbv NP: "IC Node Provider Bianca-Martina Rohner | pc1"
room: ic-node-provider-i3cfo NP: "IC Node Provider Conic Ventures | ld1 ns1"
room: ic-node-provider-otzuu NP: "IC Node Provider Geeta Kalwani | bg1"
room: ic-node-provider-s5nvr NP: "IC Node Provider Mariano Stoll | ar1"
room: ic-node-provider-vdzyg NP: "IC Node Provider Mary Ren | sj1"
room: ic-node-provider-3siog NP: "IC Node Provider Mika Properties, LLC | tp1"
room: ic-node-provider-hk7eo NP: "IC Node Provider NoviSystems, LLC | fm1"
room: ic-node-provider-trxbq NP: "IC Node Provider Privoxy Solutions, LLC | dr1"
room: ic-node-provider-n32q7 NP: "IC Node Provider Adam Dymecki | fm1"
room: ic-node-provider-mjnyf NP: "IC Node Provider Bitmoon | ba1 li2"
room: ic-node-provider-2wxxr NP: "IC Node Provider Brener, Inc. | sj1"
room: ic-node-provider-67gkg NP: "IC Node Provider Fritz Huie | sj1"
room: ic-node-provider-7ws2n NP: "IC Node Provider InfoObjects | sj3"
room: ic-node-provider-5zqo2 NP: "IC Node Provider Jeffrey Schnettler | tp1"
room: ic-node-provider-sdal5 NP: "IC Node Provider Moon Block Ventures | sj1"
room: ic-node-provider-72idx NP: "IC Node Provider Peggy Shafaghi | fm1"
room: ic-node-provider-q22bo NP: "IC Node Provider Ricky Sidhu | sj1"
room: ic-node-provider-wwxec NP: "IC Node Provider Ronnie Pellizzari | at1"
room: ic-node-provider-6mifr NP: "IC Node Provider Wolfhound LLC | at1"
room: ic-node-provider-pa5mu NP: "IC Node Provider Zenith Code LLC | nd1"
room: ic-node-provider-hzqcb NP: "IC Node Provider Zondax AG | zh5"
room: ic-node-provider-uvawj NP: "IC Node Provider A Dog's Boutique, LLC | at1"
room: ic-node-provider-l2kri NP: "IC Node Provider Arjay LLC | sj1"
room: ic-node-provider-7nxxb NP: "IC Node Provider CRM52 Systems, LLC | sj1"
room: ic-node-provider-olgti NP: "IC Node Provider DRMxTech Enterprises, LLC | sj1"
room: ic-node-provider-ob633 NP: "IC Node Provider Fidgitville Ventures LLC | sj1"
room: ic-node-provider-myrs2 NP: "IC Node Provider Goodsir, LLC | fm1"
room: ic-node-provider-qcs4o NP: "IC Node Provider Jonathan Ziskind | sj1"
room: ic-node-provider-abscc NP: "IC Node Provider Lauren Dymecki Chickvara | tp1"
room: ic-node-provider-4anlt NP: "IC Node Provider Mitchel Guerra | tp1"
room: ic-node-provider-chnsu NP: "IC Node Provider Rachel Dymecki | at1"
room: ic-node-provider-cmcjw NP: "IC Node Provider Richard Suarez | fm1"
room: ic-node-provider-bgprp NP: "IC Node Provider Rodney Zorrilla | fm1"
room: ic-node-provider-p5jx4 NP: "IC Node Provider Russell Ford | at1 "
room: ic-node-provider-usau7 NP: "IC Node Provider William Zelver | sj1"

Neat!:) The space makes things much more clear, especially for people who have more projects going on in their matrix account.

However, I have a problem joining the room that should be created for me (it is also not listed in the space and I had to search; my identifier is efem5)

MatrixError: \[403\] You are not invited to this room.

Dear all,

We are pleased to announce that the recovery process for the ex-uzr34 nodes is now ready. We apologize for the extended timeline in developing this process, but we used the opportunity to create a recovery image that can be applied in a broader range of scenarios, rather than just for the uzr34 nodes -- for instance in a potential case of a complex NNS subnet recovery.

The nodes listed below were taken offline due to the incident detailed at this forum link.

Some node providers have already redeployed the affected nodes from scratch, which is completely acceptable. If you prefer this route, you can follow the steps outlined in the Troubleshooting Node Deployment Errors guide.

However, it would be beneficial for everyone if you could use a special one-time use OS image we've prepared for this specific case. This bootable image, distributed as an ISO file, will remove the corrupted data from the incident and restore the node to a usable state (i.e., a fresh node not assigned to any subnet). The node will then be manageable like any other node on the Internet Computer.

To apply the recovery process, please follow these steps:

1. Download the recovery image:

   • Obtain the bootable ISO file "recoveryos.iso" and the checksum file "sha256sums.txt" from this Google Drive link.
   • Verify the checksum of the ISO file against the one listed in "sha256sums.txt" to ensure the file was downloaded correctly.

2. Boot the node from the ISO file:

   • Recommended: If you have remote access to the BMC web interface of the machine, boot the machine from the ISO file through BMC.
   • Alternative: If remote access is not available, write the ISO file to a USB drive using a tool like Rufus, Balena Etcher, or UNetbootin. Connect the USB to the node, reboot the machine, and select the USB drive as the boot device in the UEFI/BIOS boot menu. Instructions for this process can be found in the Node Deployment Guide.

After applying the fix, the machine's operating system should automatically reboot into the regular IC-OS, and the node should come back online.

Please ensure that the recovery image is used only for the affected nodes. Booting any other nodes from this image will result in data loss, requiring a complete re-provisioning from scratch.

We appreciate your continued support of the Internet Computer infrastructure.

Best regards,
DFINITY Team

node_id: 'Node Provider'
njrl2-xk3tb-n662s-ckjbn-a6nrw-efzr2-o2352-su2lq-csj4k-pjlgs-rqe: 'Icaria Systems Pty Ltd'
ljfwz-ol5ig-7fsu7-4vznl-52eyn-xw76h-uls7q-35qlu-t3hfh-5kyu5-oae: 'Lukas Helebrandt'
4ifvf-q4djg-kzooi-5xvs6-66adz-6mysk-c2bz6-osuin-mgh7f-rzgxu-hqe: 'MI Servers'
vdh6o-dmg2b-cnryk-ltyjq-yda26-rdfuo-ucf3h-wiusa-nbi2w-tcnqs-bae: Origin Game'
kv6uy-34zmz-jarp7-fcss3-acfwy-abqbn-xwqac-hhqz6-ioq4u-b6f35-hae: 'Illusions In Art (Pty) Ltd'
wo25n-k5g37-sc6et-n5vpz-xpsrn-t23xp-rrs5j-d5fy2-ibfny-5vrd7-mqe: 'Giant Leaf, LLC'
bbagu-dnle7-gc3zz-7dqkj-aflcj-c5nvr-w36w6-zbk6x-mutkh-sj55s-yqe: 'ACCUSET SOLUTIONS'
xqhoe-c5pck-wcytx-owvyr-mntbp-u22ct-nvcqi-bri5w-sjow2-rs4gp-sae: 'George Bassadone'
7ftkg-pfsde-ti2e3-ei5b5-liglh-uazwu-liej7-2fqco-7izqv-cxqqr-fae: 'Maksym Ishchenko'
nepju-cofjr-c4nxg-33d7t-yyka7-d6k7o-xhevc-z76ns-ej43t-jcblv-rae: 'OneSixtyTwo Digital Capital'
f4nlw-f6qsm-hxf5k-mkjr6-q5jgn-imnys-fhbhr-jzmxm-73iha-gpbji-oqe: '7at4h-nhtvt-a4s55-jigss-wr2ha-ysxkn-e6w7x-7ggnm-qd3d5-ry66r-cae'
vv3vr-t64kd-5m2ev-spobj-5xdx6-2zu6s-5gdf2-mnmsy-bdn5c-j24jk-hae: 'DRMxTech Enterprises, LLC
fzclq-uw6cm-gw5nv-j2iyy-zeiu5-qqw4i-5x4cs-csrw5-pquah-xspkw-uae: 'Iancu Aurel'
vs5lv-6h44x-qfalu-aesc6-uehxl-zlwiu-5z7ik-c3kjy-6vtxl-3yz7x-qae: Anonstake'

In reply to @andrewbattat:matrix.org
In the meantime, I suggest you try to redeploy using the latest version and see if that solves your issue (you're using a version from August 26th)

we've tried different versions and every time the problem persists.

I look forward to hearing more from you

hi 77676m just a quick update to say that the it looks like the clock on your machine is behind by a ~12 minutes which seems to be causing issues with it registering.

Normally there is a chrony service that keeps the clock in sync. We're not sure why it is not syncing.

hi 77676m just a quick update to say that the it looks like the clock on your machine is behind by a ~12 minutes which seems to be causing issues with it registering.

Normally there is a chrony service that keeps the clock in sync. We're not sure why it is not syncing.

Is it possible that something is blocking NTP traffic (UDP port 123) ?

In reply to @raymondk:matrix.org

hi 77676m just a quick update to say that the it looks like the clock on your machine is behind by a ~12 minutes which seems to be causing issues with it registering.

Normally there is a chrony service that keeps the clock in sync. We're not sure why it is not syncing.

Is it possible that something is blocking NTP traffic (UDP port 123) ?

In reply to @77676m:matrix.org
Hi, thanks, problem solved, I set the correct time and registration was successful

In reply to @sasa-tomic:matrix.org
Do you have some firewall that could be preventing ntp sync?

In reply to @raymondk:matrix.org
Hi 77676m, glad things have improved. Could you explain where and how exactly you changed the time?