If you can connect over SSH why not just tunnel over SSH?
"-bmanagement=_external_ip_address" should be supported as well as you can pass 0.0.0.0.
What's the error message you got?
Eduard, I think there is misunderstanding of -bmanagement option from your side. It is saying which IP wildfly listen on. So if you set -bmanagement=_external_ip_address and _external_ip_address is ip of your personal computer - it can't work. By saying -bmanagement=0.0.0.0 wildfly will listen on all interfaces of virtual private server.
So I would recommend to not specify -bmanagement, what is effectivelly equivalent to -bmanagement=127.0.0.1 - that allows only local acces and as Darran said utilize SSH tunnel.
Thank you all for your comments.
Martin Chome, Daren Lofthouse, you are probably right. Its become increasingly clear to me that I should study the documentation more closely to figure this one out (and general topics like socket binding / ssh port forwarding)
Yoshimasa Tanabe, the error is something along the lines of "Failed to start service network.management ... failed to resolve interface management"
if it was like the following log, _external_ip_address you passed is invalid. please check the machine NIC ip address.
02:47:47,638 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-7) MSC000001: Failed to start service jboss.network.management: org.jboss.msc.service.StartException in service jboss.network.management: WFLYSRV0082: failed to resolve interface management
ofc, you can choose ssh tunneling(and not passing -bmanagement, keep bounded with localhost) as Marin and Daren said. it's up to your use case.
Port forwarding works and it's super easy to set up. This command, run from the local machine, will do the trick:
ssh -L 9990:localhost:9990 [user@]hostname
It is then possible to access the admin console in the browser by going to http://localhost:9990/console/App.html
Hope it helps someone else.