Hi, we've been using the Confluence CLI tool for a while to export wiki pages to HTML. It stopped working in the past couple weeks:
./confluence.sh -a exportSpace -s https:/<mydomain>.jira.com/wiki -u <user> -p <pwd> --space TSUD -f docs.zip --exportType HTML
Remote error: (504)Gateway Time-out
I thought it was related to an On-Demand update, but now I'm not sure.
We have been using atlassian-cli-2.5.0, but I also tried atlassian-cli-3.3.0 and got the same result. I've tried from a few different machines/networks over the past couple weeks, but always the timeout error.
Is the timeout in the web server, or the CLI script? Any suggestions are appreciated. Thanks --rob
Timeout is 60 seconds.
I exported Confluence from On-Demand and imported it to a local server, and I am able to export fine from the local server. So I don't think there is any problem with your CLI tool, probably a web server timeout.
I also have the same problem using atlassian-cli-2.6.0 as of this week. The file has 4 tables and if I reduce the file content it works fine.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Export space can take a while. It could be it is just taking more time than before. Try using the connectionTimeout parameter.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
connectionTimeout doesn't seem to have any effect. I think the server side is what is timing out (onDemand)
Here is the connection string with the timeout parameter
./atlassian-cli-3.3.0/confluence.sh -a exportSpace -s https://iontorrent.jira.com/wiki -u ts-export -p ts-export --connectionTimeout 0 --space TSUD -f docs.zip --exportType HTML
Previously, it was failing intermittently so I would retry until it worked. But now it's failing 100% of the time with (504) error. The size of our data has probably increased over time.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
How long before the timeout? Run with --debug and verify it times out before the url to the file is generated. Maybe Atlassian might have some ideas on any way to work around that.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Online forums and learning are now in one easy-to-use experience.
By continuing, you accept the updated Community Terms of Use and acknowledge the Privacy Policy. Your public name, photo, and achievements may be publicly visible and available in search engines.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.