Does not work with VPN???

[cayennep]

I don't see any posts in this forum about this and still pretty shocked (and somewhat wondering if there's some mistake).

This renders the whole product useless for us, and I'm also surprised to see others are not mentioning it. Is it just because it's relatively new, in terms of a wide release?

Any others finding this??

[Psider]

I can't help but I just want to confirm the issue.

You work remotely and use a VPN to connect to your work network. However, when you are using a VPN, Flare cannot connect to Central?

Is that right?

[cayennep]

Yup, ‘fraid so.
However, after some back and forth and the first madcap support person telling me it does not work with vpn (which turns out not to be true, synch up folks!) I now hear they’ve had no issues.
Not sure if others are using vpn, but it’s possible ours is just too messed up to do this. Asana doesn’t work, other things have also been problematic, so it may be an issue of figuring out exactly what the vpn configs are and then trying to work around it.

Anybody else working on vpn?

[TR Lisa]

This thread makes me wonder if VPN has something to do with continually losing the Flare-to-Central connection and my commits not working. I've tried connecting without VPN and have the same issues, but I wonder if VPN is what creates the problem that then persists regardless of connection type. I'm going to bring this up on my support call with MadCap today. If VPN is the culprit it's definitely a huge problem--I have to VPN to connect to my product test environments, which I need to see while I'm documenting features in those environments.

[Michelle_Gardner]

@TR Lisa, did you get an answer about VPN causing the initial problems with committing files?

[deblockwood]

@cayennep We are just getting started with Central (I'm setting up the test environment now) and VPN is not an issue for us. I am a remote employee, use VPN (ASA) all day long, and have had no issues binding, pulling, and pushing files.