Still looks like it could be a connection problem.
The port, 443, would need to be either
- forwarded from a router to the server, making it possible to send data from external sources (like the internet) to the server, transparently through the router; or
- the sever would need to be connected directly to the public network to be able to be accessed from an external source.
And then port 443 isn’t the standard SSH port, so that wouldn’t do anything except if the personal server is configured to use that port for SSH. AFAIK port 443 is for HTTPS by default, so this is a bad idea anyway.
So basically I’m very sad to say, that command doesn’t make sense on it’s own. Perhaps if there is proper context…and for that you’d have to give a lot more info. To that end, please see:
Hope you manage!
To provide terminal output, copy the text you wish to share, and paste it here, surrounded by three (3) backticks, a.k.a grave accents. Like this:
This will just cause it to be rendered like this:
cursus nisl nisi
hendrerit ac quis
tortor sit leo commodo.
Instead of like this:
Portaest sed elementum cursus nisl nisi hendrerit ac quis sit adipiscing tortor sit leo commodo.
Alternatively, paste the text you wish to format as terminal output, select all pasted text, and click the </> button on the taskbar. This will indent the whole pasted section with one TAB, causing it to render the same way as described above.
Thereby improving legibility and making it much easier for those trying to be of assistance.
Also, if your language isn’t English, please prepend any and all terminal commands with
LC_ALL=C. For example:
This will just cause the terminal output to be in English, making it easier to understand and debug.