🎉 Before you dive into this article...
🚀 Check out our vibrant new community at CoderLegion.com!
💡 Share your knowledge, connect with like-minded developers, and grow together.
👉 Click here to join now!
That error demonstrates an organisational issue that happened eventually in the form cycle, yet it ought to (apparently here) be irregular and uncommon. If you see it, re-running the form is the most ideal alternative; on the off chance that you experience it more than once, if it's not too much trouble, open a help ticket or connect!
Problem
That blunder isn't coming from the example code, yet a web search on the bit of the mistaken text that you've given and some testing I did recommends that it's a systems administration issue (explicitly probable name goal).
I went through the cloning, building, and execution of that example without blunder. Then, at that point purposely provided terribly
• installed and tried ssh on my home organization.
• Set a static IP for my pi.
•
Set up a Powerful DNS administration and introduced the product on my pi. I referred to these guidelines for setting up the static IP, and there are a lot more informative assets out there.
Solution
Likewise, I set up a port forward on my switch for facilitating a site and I had even port forward port 22 to my pi's static IP for ssh, yet I left the field clear where you indicate the application you are playing out the port sending for on the switch. In any case, I added 'ssh' into this field and, Presto! A working ssh association from anyplace to my pi.
I worked out my switch's port sending settings.
(ApplicationTextField)_ssh (outside port)_22 (Inner Port)_22 (Protocol)_Both (To IP Address)_192.168.1.### (Enabled)_checkBox
Port forward
ssh - p 22 myName@hostname
or on the other hand:
ssh - l myName - p 22 hostname
Hope this post helped you!
Top comments (0)