Error while adding Activity Stream in Confluence
Asked by mail2sebastianpeter:

Hi all,

I am getting the following error while adding the Activity Stream in Confluence. Please suggest a solution for the problem. I have also white listed the url's and checked but no use.

**Error Message:**

Requests to [http://az\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*/rest/activity-stream/1.0/preferences](http://azurnae-ap011.northamerica.delphiauto.net:8090/rest/activity-stream/1.0/preferences) are not allowed. See your administrator about configuring a whitelist entry for this destination (<http://confluence.atlassian.com/x/KQfCDQ> ).

Please see the attached screen shot of error.![error in confluence.PNG](/t5/image/serverpage/image-id/17719i926F93DE1FE624E2/image-size/large?v=v2&px=999 "error in confluence.PNG")


Answers:
author: Anatoly Nikolaev
body: Hello, we also have same error in Confluence 6.1.1. URL in error message and our Confluence URL are different.

Error message - https://confluence/rest\*

Our Confluence - [https://confluence.int."mycompany"/rest\*](https://confluence.int."mycompany)

comments: author: Shannon S
body: Hello Anatoly,

You'll want to make sure that the URL is added to your [Confluence Whitelist](https://confluence.atlassian.com/doc/configuring-the-whitelist-381255821.html). You can also try to [reconfigure the external gadget URL](https://confluence.atlassian.com/doc/registering-external-gadgets-204050482.html).

If it continues to throw the error, you will want to look at your [Confluence Server logs](https://confluence.atlassian.com/doc/working-with-confluence-logs-108364721.html) when you trigger the error. It will tell you there what the exact cause of the problem is.

One more thing; your Confluence version of 6.1.1 is at risk. That version has reached [End of Life](https://confluence.atlassian.com/support/atlassian-support-end-of-life-policy-201851003.html) on 20 March, 2019. In addition, we had a pair of security vulnerabilities announced over 6 months ago. In order to avoid compromise, you should upgrade Confluence as soon as possible. See [Confluence CVEs and common questions](https://community.atlassian.com/t5/Confluence-articles/Confluence-CVEs-and-common-questions/ba-p/1062634) for more details.

Let me know if you have any questions about that.

Regards,

Shannon


author: Anatoly Nikolaev
body: This Activity Stream was internal, but it has been changed to not actual for us https://confluence/ by some reason. And now we see error in previosly added Activity Streams and if try to add new standard Activity Stream to page.


author: Shannon S
body: Anatoly,

Thank you for your reply. If you are still encountering this issue, then please have a look at your Server logs per my suggestion and we can proceed from there!

Regards,

Shannon


author: Anatoly Nikolaev
body: The problem has been solved after restart Confluence server.


author: Shannon S
body: Hi Anatoly,

That's good news! Thank you for letting me know that.

If the issue comes back, please let us know.

Take care, and have a pleasant rest of your week.

Regards,

Shannon


author: Shannon S
body: Sebastian,

Can you confirm with us your Confluence version, if the URL you blacked out is the same as the Confluence instance, and if you're running behind a proxy or firewall?

Do you happen to see any error messages within [your Confluence logs](https://confluence.atlassian.com/doc/working-with-confluence-logs-108364721.html) that will give us further information?

Regards,

Shannon

comments: author: mail2sebastianpeter
body: We are using the confluence version 6.2.4

The url that i blacked out is an azure server location.

I am also attaching the log analyzer with this.![confluence_log.PNG](https://community.atlassian.com/t5/image/serverpage/image-id/17732i6C277C31BA15F939/image-size/large?v=v2&px=999 "confluence_log.PNG")

If you think anything to be resolved in this log please tell as i am new to confluence.


author: Shannon S
body: Sebastian,

The messages in the screenshot don't pertain to the issue you're having currently.

My recommendation is to check the log file itself from your server. You can tail it while you trigger the error from earlier, and it should give you further information about the problem.

Regards,

Shannon