I get an invalid HTTP request (302) error. Can't sync. about wordpress-github-sync

[mAAdhaTTah]

A 302 is a temporary redirect. You're getting this on the initial export?

[wolffe]

Yes. The repository was created 30 minutes earlier.

EDIT: I'm getting this inside github, don't know if it's import or export.

[mAAdhaTTah]

Have you done a full export first? On the settings page, fill out all the info then click export to GitHub.

And by "inside GitHub", you mean on the webhook response?

[wolffe]

Yes, I have done a full export first, I got a "successful" notification, but nothing was exported.

And yes, I mean the webhook response.

[mAAdhaTTah]

So, just to get a step-by-step view of what happened:

1. You input all the settings correctly on the settings screen (/wp-admin/options-general.php?page=wordpress-github-sync) and clicked save.
2. You clicked "Export to GitHub" on the same settings page, and when the page loaded again, it said "Export to GitHub started" (or something to that effect, I can't remember the message offhand; but it said Started).
3. You waited a minute or two, then went back to the settings page to see "Export to GitHub Successful".
4. You checked the webhook on GitHub and it gave you a 302. (Can you provide the full message here?)

Is this correct?

Thanks!

[wolffe]

It is correct, yes. The exact message was:

Invalid HTTP request: 302.

I have deactivated the plugin for now.

Note: It could be related to Cloudflare's SSL, which is not exactly a full SSL certificate. You might want to investigate that.

[mAAdhaTTah]

Are you using this plugin? This might be outside of our ability to do anything about.

[mAAdhaTTah]

Maybe check if ajax requests are handled properly by that plugin or your current setup. The weird thing is this should really affect outgoing GitHub requests, just the incoming one, so it wouldn't completely explain why you're not able to export.

[wolffe]

No, I'm using this one for HTTPS fixes - http://mvied.com/projects/wordpress-https/ - and a free Cloudflare plan.

[wolffe]

I'll try to deactivate the SSL tonight and test it again.

[mAAdhaTTah]

If you have any additional issues with this, I'll try and help you out, but this seems like a problem beyond our control, so closing for now.