How to fix "Unknow Error" when trying to add users to groups?

[Marcia Lima]

I am using Bitbucket Data Center on a docker container which is also connected to PostgreSQL (hosted on another docker container).

I am able to create users and groups, however I am unable to add the created users to the groups I have established. Every time I try to to conclude the action I get the following error: "An unknown error has occurred."

What is causing this and how can I fix it?

[Stephen Sifers]

Hello Marcia and welcome to the Community!

To figure out what is causing this, we will need to see more about the exact error which is occurring. Could you please follow these steps and let us know the results:

1. For Bitbucket go to > Administration > Troubleshooting and support tools (underSupport)
2. Select Log analyzer, allow it to complete
3. Please let us know the results which are displayed.

Once we have an idea of what the error is in regards to we can assist with finding a solution.

Regards,
Stephen Sifers

[Marcia Lima]

Hi Stephen,

When I try to get the logs via the instructions you have provided I get no logged results.
So, I tried accessing the logs within the container and got the following warnings:

2019-02-06 00:56:22,236 WARN  [Caesium-1-4]  c.a.a.c.h.r.RemoteHashingInstructionsReader Unable to read remote instructions with key 'uid.onewayhash'.
2019-02-06 00:56:22,237 WARN  [Caesium-1-4]  c.a.a.c.h.BcryptAnalyticsEmailHasher No instructions for hashing could be found.
2019-02-06 09:20:47,829 INFO  [Caesium-1-3]  c.a.b.i.s.c.j.c.HealthCheckRunner Running up to 2 search health checks
2019-02-06 09:20:47,841 INFO  [I/O dispatcher 241]  c.a.b.s.s.t.DefaultElasticsearchConnectionTester Connected to Elasticsearch version 5.5.3
2019-02-06 09:20:47,857 INFO  [Caesium-1-3]  c.a.b.i.s.c.j.c.HealthCheckRunner Health checks will run again after PT12H
2019-02-06 11:33:46,198 WARN  [http-nio-7990-exec-8] dev2ops @4J1P0Qx693x2997x0 1nobcz4 10.59.21.27,172.19.0.1 "POST /rest/analytics/1.0/publish/bulk HTTP/1.0" c.a.p.r.c.s.j.XsrfResourceFilter Additional XSRF checks failed for request: http://my-company.bitbucket.:7990/rest/analytics/1.0/publish/bulk , origin: http://my-company.bitbucket , referrer: http://my-company.bitbucket/admin/server-settings , credentials in request: true , allowed via CORS: false
2019-02-06 11:33:48,793 INFO  [I/O dispatcher 253]  c.a.b.s.s.t.DefaultElasticsearchConnectionTester Connected to Elasticsearch version 5.5.3

I hope this helps, because I am pretty new to this nad I not sure on what could be causing this issue.

Thanks.

[Marcia Lima]

Hi Stephen,

When I try to get the logs via the instructions you have provided I get no logged results.
So, I tried accessing the logs within the container and got the following warnings:

2019-02-06 00:56:22,236 WARN  [Caesium-1-4]  c.a.a.c.h.r.RemoteHashingInstructionsReader Unable to read remote instructions with key 'uid.onewayhash'.
2019-02-06 00:56:22,237 WARN  [Caesium-1-4]  c.a.a.c.h.BcryptAnalyticsEmailHasher No instructions for hashing could be found.
2019-02-06 09:20:47,829 INFO  [Caesium-1-3]  c.a.b.i.s.c.j.c.HealthCheckRunner Running up to 2 search health checks
2019-02-06 09:20:47,841 INFO  [I/O dispatcher 241]  c.a.b.s.s.t.DefaultElasticsearchConnectionTester Connected to Elasticsearch version 5.5.3
2019-02-06 09:20:47,857 INFO  [Caesium-1-3]  c.a.b.i.s.c.j.c.HealthCheckRunner Health checks will run again after PT12H
2019-02-06 11:33:46,198 WARN  [http-nio-7990-exec-8] dev2ops @4J1P0Qx693x2997x0 1nobcz4 10.59.21.27,172.19.0.1 "POST /rest/analytics/1.0/publish/bulk HTTP/1.0" c.a.p.r.c.s.j.XsrfResourceFilter Additional XSRF checks failed for request: http://my-company.bitbucket.:7990/rest/analytics/1.0/publish/bulk , origin: http://my-company.bitbucket , referrer: http://my-company.bitbucket/admin/server-settings , credentials in request: true , allowed via CORS: false
2019-02-06 11:33:48,793 INFO  [I/O dispatcher 253]  c.a.b.s.s.t.DefaultElasticsearchConnectionTester Connected to Elasticsearch version 5.5.3

I hope this helps, because I am pretty new to this nad I not sure on what could be causing this issue.

Thanks.

[Stephen Sifers]

Hello Marcia,

Thank you for checking the support tools along with sending the above logs. While these logs do tell us something, they don't tell us why you're having this issue.

The logs we're looking for will be in the Bitbucket home path. The file will be called atlassian-bitbucket.log. If possible, trigger the error again by performing an add user action. Then please review the logs and locate all recent "Caused By" records within the log. We will need the parts of the log above the caused by and below until the indention has ended.

Here is an example of what we will need from your logs (This is an example of what the caused by looks like, your event will be much different from this):

2016-12-07 07:26:58,108 http-nio-8080-exec-22 ERROR user 446x4928x1 f7vyfp 0.0.0.0 / [ContainerBase.[Catalina].[localhost].[/]] Unhandled exception occurred whilst decorating page
java.lang.RuntimeException: javax.servlet.ServletException: java.lang.RuntimeException: com.google.template.soy.tofu.SoyTofuException: In 'print' tag, expression "$dashboardTitle" evaluates to undefined.
    at com.atlassian.web.servlet.plugin.DynamicAuthorizationServletForwarder.forward(DynamicAuthorizationServletForwarder.java:55) [?:?]
    at com.atlassian.web.servlet.plugin.SanitizingServletForwarder.forward(SanitizingServletForwarder.java:32) [?:?]
    at com.atlassian.web.servlet.plugin.RememberingServletForwarder.forward(RememberingServletForwarder.java:51) [?:?]
    at com.atlassian.web.servlet.plugin.ResolvingServletForwarder.forward(ResolvingServletForwarder.java:38) [?:?]
...
Caused by: javax.servlet.ServletException: java.lang.RuntimeException: com.google.template.soy.tofu.SoyTofuException: In 'print' tag, expression "$dashboardTitle" evaluates to undefined.
    at com.atlassian.jira.web.dispatcher.JiraWebworkActionDispatcher.onActionException(JiraWebworkActionDispatcher.java:220) [classes/:?]
    at com.atlassian.jira.web.dispatcher.JiraWebworkActionDispatcher.service(JiraWebworkActionDispatcher.java:172) [classes/:?]
...
Caused by: com.google.template.soy.tofu.SoyTofuException: In 'print' tag, expression "$dashboardTitle" evaluates to undefined.
    at JIRA.Dashboard.page.dashboard(dashboard.soy:12) [?:?]
    at com.google.template.soy.tofu.internal.BaseTofu.renderMainHelper(BaseTofu.java:369) [?:?]
    at com.google.template.soy.tofu.internal.BaseTofu.renderMain(BaseTofu.java:322) [?:?]
    at com.google.template.soy.tofu.internal.BaseTofu.access$100(BaseTofu.java:66) [?:?]
    at com.google.template.soy.tofu.internal.BaseTofu$RendererImpl.render(BaseTofu.java:476) [?:?]
    at com.atlassian.soy.impl.DefaultSoyTemplateRenderer.render(DefaultSoyTemplateRenderer.java:45) [?:?]
    at com.atlassian.soy.impl.DefaultSoyTemplateRenderer.render(DefaultSoyTemplateRenderer.java:39) [?:?]
...

Once we have the caused by logs we should be able to see what is causing this error.

Regards,
Stephen Sifers

[Marcia Lima]

Hi Stephen,

I performed the process to add na user to a group I have previously created and I got this error:

 2019-02-06 15:12:14,426 WARN  [http-nio-7990-exec-10] user @4J1P0Qx912x3068x0 12mkbay 10.59.21.27,172.19.0.1 "POST /rest/analytics/1.0/publish/bulk HTTP/1.0" c.a.p.r.c.s.j.XsrfResourceFilter Additional XSRF checks failed for request: http://my-company.bitbucket.com:7990/rest/analytics/1.0/publish/bulk , origin: http://my-company.bitbucket.com , referrer: http://my-company.bitbucket.com/admin , credentials in request: true , allowed via CORS: false
 2019-02-06 15:12:35,941 WARN  [http-nio-7990-exec-1] user @4J1P0Qx912x3091x0 12mkbay 10.59.21.27,172.19.0.1 "POST /admin/groups/add-users HTTP/1.0" c.a.p.r.c.s.j.XsrfResourceFilter Additional XSRF checks failed for request: http://my-company.bitbucket.com:7990/rest/api/1.0/admin/groups/add-users , origin: http://my-company.bitbucket.com , referrer: http://my-company.bitbucket.com/admin/groups/view , credentials in request: true , allowed via CORS: false

Do you think you can Help understand what might be wrong here?
I assumed it was the database, but the version I have for PostgreSQL is 10.6-alpine (running on docker container within the same container network) and it seems to be supported by the version I have for the Bitbucket server (Data Center).

[Stephen Sifers]

Hello Marcia,

Thank you for testing this and sending over the results. You’re errors you sent over are very similar to issues with a proxy being used with Bitbucket, but Bitbucket is unaware of the proxy itself. There was a post which does an excellent job explaining what needs to be done to resolve this error. You may find that post at Can't create branch after updating stash to bitbucket.

Within that post, they recommend editing your configuration file to make Bitbucket aware of the change. The edit will be done on your server.xml file and includes the following:

server.secure=true
server.scheme=https
server.proxy-port=443
server.proxy-name=mycompany.com

Please let us know if this helps with resolving your issue.

Regards,
Stephen Sifers

[Marcia Lima]

Hi Stephen,

I have located the file and it has the same parameters as you have shown above... Is there any other way to tackle this?

Thank you for your support so far.

Best Regards

[Stephen Sifers]

Hello Marcia,

To further look into this issue I have created a support request on your behalf. You should be receiving an email shortly with the support details.

Regards,
Stephen Sifers