New to MOZ, can't create a campaign.

[jcsilkey]

I just started the free trial today, but I can't setup a campaign. Everywhere I go (http://analytics.moz.com/pro/home, http://analytics.moz.com/manage-campaigns), all I see is:

Oops! Try refreshing the page, if that doesn't work, please click here to contact our help team.

Is something broken?

[jcsilkey]

To answer my own question, the problem seems to have been network/firewall related.  When I switched to a different internet connection, everything started working fine...

[KeriMorgret]

So glad to hear that, and thanks for letting us know that it's fixed!

[jcsilkey]

I did a little more digging, and here's what I found.  When connected to the network in question, I get numerous errors in the browser console like this when loading the pro home or campaign pages:

XMLHttpRequest cannot load http://vanguard.moz.com/pro-home/campaign-list-lite/prod.3938937\. Origin http://analytics.moz.com is not allowed by Access-Control-Allow-Origin. (home, line 0)

I do not get those errors (at least I have not thus far) when connected to other networks. I don't know much about the network setup here, but I do believe there is a proxy in place.

[KeriMorgret]

If you do have problems in the future, could you send us a note at help@moz.com? There's some one-on-one help we can give you with a couple of alternatives. Thanks!

[DavidLee]

Hey!

This is somewhat of a common issue with strange configuration issues with specific machines. Especially on Macs.

Our engineers have identified three possible causes and solutions for this issue:

1. Highly sensitive anti-virus software. The way to get around this is to whitelist moz.com in the software. If you are running Sophos Anti-Virus on Mac. Disable the option 'Block malicious downloads from websites, protecting your Mac from obfuscated, polymorphic and zero-day threats before reaching your browser'.

2. Enterprise firewalls that block us, which you may need to work with your IT department on if you do not have direct access to your firewall settings.

3. VPN connection/profiles. Disabling or removing the VPN profile has been known to be a common issue.

We confirmed that the problem was the Cisco AnyConnect client installed on his machine. Even if the client isn't actively running, a background service it installs blocks CORS requests. Uninstalling it allowed him to use MA immediately.

Here's an article describing the problem, and a possible workaround:
http://www.bennadel.com/blog/2559-cisco-anyconnect-vpn-client-may-block-cors-ajax-options-requests.htm

Ultimately our guess is a software update is compromising key security files that are preventing access to ajax options requests and a last resort fix has been a re-install of an OS. It's very tricky but hopefully one of the above issues is the culprit, which can be fixed.

Hope this helps!