use serveo.net generate link for HTTP server

[Davider]

http://localhost:4455/Simple

Using the above link returns results. (https://www.libreautomate.com/forum/show...6#pid36746)

However, generating the link using the following method and then accessing the link does not return results.
PS: Using serveo.net to generate a link may be the simplest method.
 

 
ssh -R 80:localhost:4455 serveo.net

[Gintaras]

What other local HTTP server software did you test with serveo? How does it work?

[Davider]

What other local HTTP server software did you test with serveo?

Using the built-in OpenSSL component in the Windows system.
https://i.ibb.co/CnfbpD6/A.png

https://serveo.net/

The official website provides the following description

Alternatives:

ngrok
Serveo is an excellent alternative to ngrok. Serveo was inspired by ngrok and attempts to serve many of the same purposes. The primary advantage of Serveo over ngrok is the use of your existing SSH client, so there's no client application to install.
Other slight advantages include preservation of URLs across reconnect for free (ngrok allows this only for paid accounts) and in-terminal request inspection and replay (ngrok uses a web interface).

OpenSSH
erverUsing Serveo instead of OpenSSH frees you from having to configure and maintain a server. It also handles HTTPS and subdomain generation, two features that complicate a typical SSH port-forwarding setup.

[Davider]

@Gintaras

My operating steps are as follows:
https://i.ibb.co/MD0W3Mt/AA.gif

---

It worked! I forgot to add the function at the end of the link.
format:
https://baf32aafxxxxxxxxxxxxxxxxxxx.serveo.net/Simple

---

This is the simplest method I found, and it supports HTTPS as well.

---

I believe this method should be added to the help documentation of the HTTP Server class. It's truly exciting! 

[Davider]

Existing issues:
1. The system's built-in Openssh component needs to be manually added in the system's Control Panel or using the following PowerShell command:
   Add-WindowsCapability -Online -Name OpenSSH.Client~~~~0.0.1.0
2. After executing the command in PowerShell to generate the link, it is temporary, and the command prompt window cannot be closed, otherwise, the link will become invalid.

Resolving them:
Could SSH.NET component be used and executed asynchronously?
Could someone share the code for this functionality? Thank you very much.

[Davider]

It would be great if a switch could be added.
When I enable it, it could use the command (ssh -R 80:localhost:4455 serveo.net) or the SSH.NET component to generate a publicly accessible link in the output panel. 

[Gintaras]

My web browser can't connect to serveo.net today.

I don't see problems with ngrok. It gives a free static URL. With it the ngrok agent can run hidden:

Code:

Copy      Help

process.terminate("ngrok.exe");

string ngrok = @"C:\Downloads\ngrok.exe";
string cl = "http --domain=my-static-domain.ngrok-free.app 4455";

run.it(ngrok, cl); //visible
//run.it(ngrok, cl, dirEtc: new() { WindowState = ProcessWindowStyle.Hidden }); //hidden
//run.it(ngrok, cl, flags: RFlags.WaitForExit, dirEtc: new() { WindowState = ProcessWindowStyle.Hidden }); //hidden, wait
//run.console(ngrok, cl); //hidden, wait

[Davider]

Thanks for your help.
The file ngrok.exe is too large, over 28MB, and it requires account registration, which is not very convenient. Serveo.net requires no installation and no registration.

After executing the above code, the CMD window will automatically close.
I used the following command to execute it in CMD, and the error shown in the picture below occurred. 
ngrok.exe http --domain=hello123.ngrok-free.app 4455
https://i.ibb.co/FgBWnrm/ng.png
 

---

The project in the link below allows to deploy Serveo on own server, but it requires a Linux system, while my server is a Windows system.
https://github.com/taichunmin/docker-serveo-server

[Davider]

https://github.com/antoniomika/sish
I found an open-source alternative to ngrok and Serveo. It is actively maintained, supports self-hosting, and is compatible with various systems including Windows. However, the documentation lacks detailed deployment instructions for Windows(my server is Windows server 2016).