ssh doesn't work after stoping all open-vpn services

Hi Matej,

Thanks for taking the time to file a bug and making Ubuntu server better.

Unfortunately, the site that you're using to set up isn't quite the official one, I am afraid. It uses scripts that aren't really recommended and might lead to problems that we can't help with, for example, what's exactly happened here.

I, thus, would recommend you to follow the official guide we have:
https://ubuntu.com/server/docs/service-openvpn
and see if this works as you expected?

At the moment, I am marking this bug as "Invalid" for the above reasons, but should you still hit the same bug after trying the official guide, let me know here by marking the status back to "New" and then we can work out something together.

Thanks again and hope this helps!

Hello thanks for the update, I didn't specify this at first, but for the first install, I used the script, but the second and third time I installed it manually according to the official documentation. I don't really know if this changes something but I am just specifying I installed it according to the manual for the second and third time.

thanks

Sorry for the more comments. But to clarify another thing, I haven't even "started" the VPN, I just installed it. I have just configured the port, TCP/UDP, and name of the machine on the VPN.

By the way, thanks for the comment.

Hi Matej,

Thank you for your reply. It looks like that after the first installation, some configurations got messed up or changed, due to which you're no longer to use openvpn as expected.

> I have just configured the port, TCP/UDP, and name of the machine
> on the VPN.

If you don't mind, could I ask you to undo all the changes you've made following the mentioned guide and then re-do everything as mentioned in the official docs/guide? Maybe this should help sort out the problems already, but should you still have issues, please write back with the problems and the logs (if any?) so that we can better analyze and help you here.

I am changing the status of the bug from "Invalid" to "Incomplete" at the moment. Once you've retried and reported your findings again, please set the status back to "New".

Thanks, once again.

hello, thanks for the update. But I completely reinstalled the machine every time I tried to reproduce it, just to get around this possible problem.

thanks again.

Hello Matej,

> But I completely reinstalled the machine every time I
> tried to reproduce it, just to get around this possible
> problem.

Oh? I am not sure what you mean? In a fresh machine, following the official guide, can you still reproduce this issue? Or does everything fine then?

For me, following the official guide in a fresh machine works fine for me, I guess.

Following some third-party guides and editing configurations sometimes can be troublesome and might lead to problems like these. I believe this is an example of a local configuration issue. For such cases, you can find assistance here: http://www.ubuntu.com/support/community.

But that said, I'm still interested to know if you can reproduce the same problems as reported when following the official guide in a fresh instance or machine.

Thanks!

Hello, yeah I reproduced it every time completely fresh install only with packages I had written down earlier.
And I just installed the VPN and configured some real basic things. And it just won't work (the ssh). As I said, output of "netstat -tupan" was the same as on "healthy" machine. Also, I checked with "nc -z -nv 127.0.0.1 20-80 " and it was ok.

If you feel like it we can hop on voice chat so we don't have to write everything(Just a suggestion, my English isn't perfect :D )

thanks

Thank you for taking the time to report this bug and helping to make Ubuntu better.

Since it seems likely to me that this is a local configuration problem, rather than a bug in Ubuntu, I'm marking this bug as Incomplete.

If indeed this is a local configuration problem, you can find pointers to get help for this sort of problem here: http://www.ubuntu.com/support/community

Or if you believe that this is really a bug, then you may find it helpful to read "How to report bugs effectively" http://www.chiark.greenend.org.uk/~sgtatham/bugs.html. We'd be grateful if you would then provide a more complete description of the problem, explain why you believe this is a bug in Ubuntu rather than a problem specific to your system, and then change the bug status back to New.

I really think this is a "real" bug ( I can't be sure but i think so). So should I include more information, or make a new ticket? I can definitely include the command history.

Thanks for your help

@mateeees if you still think this is a bug you can provide detailed steps on how to reproduce it in a new system. Please, do not provide steps using scripts found in non-official tutorials on the internet, they are not supported by us. In case we reproduce it locally this becomes actionable, until there it will keep as Incomplete. And no need to file another bug, once you provide the steps to reproduce it you can change the status of the bug back to New.

[Expired for openvpn (Ubuntu) because there has been no activity for 60 days.]