1.0 beta 5 not connecting; backend status: stopped

beta 6 appears to have a working backend. However, I can't get it to make a useable tunnel connection.

If I only drag my ssh server into the profile it connects just fine (but doesn't provide any functionality). As soon as I drag the services defined in the remote hosts (which are children of that ssh server), the connection fails with the following error, and then times out with "failed to connect session."

{{{ LOG:07/19 17:17:46|SEVERE|com.leapingbytes.almostvpn.server.profile.item.impl.SSHPortForward|title: Fail to build title

LOG:07/19 17:17:46|SEVERE|com.leapingbytes.almostvpn.server.profile.item.impl.SSHPortForward|title: Fail to build title LOG:07/19 17:17:46|SEVERE|com.leapingbytes.almostvpn.server.profile.item.impl.SSHPortForward|title: Fail to build title

STATE:07/19 17:17:46|starting|ProfileName|User action}}}

I have to admit though, I'm a little fuzzy with this new interface; I just don't get it. So I have probably done something wrong.

First of all, sorry for delay. Secondary, sorry that I did not mentioned it before that you do not have to uninstall 0.9.x in order to use 1.0.x. They can coexist without any problems.

Once you dragged your ssh server to profile, it will make AlmostVPN to create "host alias". You can change host alias name but by default AlmostVPN will define new host name as <ssh server name>-avpn. All services, drives, printers ... defined as a children of your ssh server will become available via this new host name. For example, if you have HTTP server running on your ssh server, than you should be able to point browser to <ssh server name>-avpn and it will take you to that HTTP server.

Have you take a look at How To(s)?

I do not like "Fail to build title" message in your log. Could you please either e-mail to support@leapingbytes.com or attach to this ticket following file:

~/Library/Preferences/com.leapingbytes.AlmostVPNPro.plist

This file does not contain any passwords (but it does contain user names and host names which you can replace with placebo it you want).

I'm sorry for my lack of understanding, but thank you for your patience.

I'm trying to use almostVPN to check my email on ports which are blocked by my university by creating a tunnel through an offsite ssh server on a network which does not block those ports. My email server is not within the private network I'm connecting to, I'm just trying to connect through the ssh server on that private network in order to talk to the publicly available mail servers, since the network the ssh server is on doesn't have the required ports blocked.

In 0.9.x, I created the SSH server and then added almostVPN connections for the pop and smtp servers. I then selected these services by clicking their checkbox for my profile. I connected with this profile, and with my mail client still set to talk to pop.hostname.com and smtp.hostname.com it worked flawlessly. I was basically using the functionality talked about in this paragraph from http://www.leapingbytes.com/documents/almostvpn/AlmostVPNConnections.html :

"As you can see, we still have port 110 on local end of the tunnel, and all packets get tunneled to port 110 on slidingpinguin. The only difference is that latte now has split personality. It still knows that it is latte, but, at the same time, it thinks that it is slidingpinguin. So, when your e-mail client trying to talk to slidingpinguin, it ends up talking to local end of the tunnel on latte. Bingo!!! From e-mail client point of view now it looks the same when you connecting from inside or from outside of your Office Network."

I assumed version 1.0 would work symilarly, which is perhaps an error. I installed it, and then went through both HowTo? articles. I assumed that I had to do something symilar to 'checking' the pop and smtp servers in the almostVPN tab of 0.9.x. First I tried dragging only the services into my profile, and got the "Fail to build title" name. Then I tried adding my ssh server along with the pop and smtp services to my profile, and got the same error. When I only put my ssh server in the profile, it connects fine, but without the functionality I expected.

I'll be happy to send you the plist file if you still wanted it, but it seems like I only got that error because I dragged the pop and smtp services to my profile, which it sounds like you aren't supposed to do, unless I'm mistaken yet again.

How should I try to duplicate this functionality in the 1.0 version?

I just published another How To. Let me know if it resolved you problem.

Good luck.