Splunk Light Trial Cloud Service: Unable to get universal forwarder credentials file. "No information of this type is associated with this XML file."

[set2016test]

Hello,

I tested Splunk Light Trial version and this trial version is on Cloud service.
So I don't have a choice, I have to download the Universal Forwarder Credentials to configure the universal forwarder.

However, when I download this file, I have 2 error results.

A web page that shows the error message:

Page not found (404) Request Method:    GET
Request URL:    http://blabla.cloud.splunk.com/dj/fr-fr/splunkclouduf/ufpackage
Using the URLconf defined in urls, Django tried these URL patterns, in this order:
    ^en-us/
    ^en-us/
    ^en-us/
    ^en-us/
The current URL, fr-fr/splunkclouduf/ufpackage, didn't match any of these.`

A web page with a message:

aucune information de ce style ne semble associé à ce fichier XML.

that means "No information of this type is associated with this XML file."

Thank you for your help.
Sophie.

[dkoshe_splunk]

Please look at https://answers.splunk.com/answering/432688/view.html for a temporary workaround, till Splunk gets this fixed.

[set2016test]

Thank you. This temporary workaround works for me.

[diogofgm · Accepted solution]

replace fr-fr in you URL with en-us

[set2016test]

Hello,
I still have the same problem with the trial version of Splunk Light on Cloud.
But this time, I can't solve this problem even with this tip to replace "fr-fr" by "en-us" in the URL of downloading link for the Universal Forwarder Credentials.

I get this error message on the web page to download the credentials :
Oops!
404 Not Found
The page requested could not be found.

Thanks again.

[gneumann_splunk]

Try this workaround, which should resolve your issue until the issue is fixed:
http://docs.splunk.com/Documentation/SplunkLight/6.4.2/ReleaseNotes/CloudUFWorkaround

[set2016test]

It works !
Thank you.

[rbittner_splunk]

Also make sure you change the url of the parent page and not the page that gives you the 404 error. The issue is with the parent page pulling up an older version of the Universal Forwader page.