# Sonarqube plugin failing due to failed export

**URL:** <https://travis-ci.community/t/sonarqube-plugin-failing-due-to-failed-export/7429>\
**Category:** Java\
**Tags:** bug\
**Created:** [March 3, 2020, 10:02am UTC](https://travis-ci.community/t/sonarqube-plugin-failing-due-to-failed-export/7429 "2020-03-03T10:02:15Z")\
**Posts on this page:** 1\
**Showing post:** 3

<div class="post-metadata">

**Author:** ![beng](https://avatars.discourse-cdn.com/v4/letter/b/b3f665/32.png) [@beng](https://travis-ci.community/u/beng)\
**Post date:** [March 5, 2020, 3:30pm UTC](https://travis-ci.community/t/sonarqube-plugin-failing-due-to-failed-export/7429/3 "2020-03-05T15:30:51Z")

</div>

Hi,

Several other users reported a similar error, which started to appear on the 1st of March:

- [ERROR: Not authorized. Please check the properties sonar.login and sonar.password - SonarCloud - Sonar Community](https://community.sonarsource.com/t/error-not-authorized-please-check-the-properties-sonar-login-and-sonar-password/21076)
- [Not authorized using travis since 1st of march - SonarCloud - Sonar Community](https://community.sonarsource.com/t/not-authorized-using-travis-since-1st-of-march/21114)

> [@native-api](#):
>
> This is because under `secure:` , you need to place the encrypted value returned by `travis encrypt` .

I tried this, but it didn’t help.  
However, if I put the encrypted value in the `.travis.yaml` file instead of in a variable, it works.

> [@native-api](#):
>
> The immediate failure and the unhelpful error message is because Travis’ logic doesn’t quote variable values as required by shell syntax if they have spaces.

The encrypted value doesn’t contain spaces… so this shouldn’t be the reason of failure…

Do you have other ideas why reading the encrypted variable could fail?

Thanks,  
Benoit

---

_[View the full topic](https://travis-ci.community/t/sonarqube-plugin-failing-due-to-failed-export/7429)._