Connected through Cisco SSL VPN to our internal Confluence Wiki it is not possible to edit content.

[Sascha Eisenblätter]

When i logon to confluence through ssl vpn tunnel i am able to create a new page with title. But i cannot create a body text content. When i am hitting "s" key a pop up is coming which asks which content i am working on.

The ssl portal is Cisco ASA based so it seems like i have to configure port mapping, opening a port - something else, but i cannot find any hints for this.

What is the action expecting? Which funcionality is recommended for http://xxx.xxx.xxx.xxx:8090/pages/editpage.action?pageId=xxxxxxxx ?

Is there a javascript function, a special placeholder???

The active link through SSL VPN looks like (for loginpage)https://xxx.xxx.xxx.xxx/+CSCO+c0756767633A2F2F31302E39352E32342E3133313A38303930++/login.action?os_destination=%2Fhomepage.action

In our LAN the system is working well.

Please support me.

[Dennis Kromhout van der Meer · Accepted solution]

To fix this you probably have to edit the Confluence Base URL to reflect your SSL address. If that doesn't fix it, please review the following documentation: Set the URL for redirection.
I know this page specifically mentions Apache, but this piece of configuration is the same for most SSL environments. Be sure to add proxyName="www.example.com",proxyPort="80" and scheme="https" to the Connector.

Good luck!

[Nader William]

we are having the same issue, but using Algo VPN, none of the atlassian.net pages are loading while behind VPN, all other URL are working and resolving just fine

[Jeff Little]

I know this is an old post... but is anyone else in this situation?

[Randall Fisher]

I'm having this issue with Jira as well, specifically the Agile boards in Jira Agile. Did you find a solution?

[greganth]

To fix this you probably have to edit the Confluence Base URL to reflect your SSL address. If that doesn't fix it, please review the following documentation: Set the URL for redirection.
I know this page specifically mentions Apache, but this piece of configuration is the same for most SSL environments. Be sure to add proxyName="www.example.com",proxyPort="80" and scheme="https" to the Connector.

Good luck!