Edition: SonarQube Developer Edition
Version: 10.6.0.0.9.92116
Deployed via zip
On any measures page I get “request failed” and in the JS console I see a 404 for
https://sonarqubeXXX.azurewebsites.net/api/measures/component?additionalFields=period&component=....
Hey there.
Our old version was: 10.4.0.87278
Nothing in the logs stood out to me. I have uploaded the access log (the only modified log file) from my attempt to reload the measures page.
measures_page_reload.logs.txt.log (19.1 KB)
Well, the 404 doesn’t show up here. 
So I’m not sure the request is making it to SonarQube! Do you have anything in between (reverse proxy, load balancer) that could be returning the 404?
There is nothing in front of the SonarQube server.
The query URL is too long by a few characters
https://XXXXXXXXXXXX.azurewebsites.net/api/measures/component?component=OutcomesMatterInnovations_omi.portal_8d57114f-7f8c-4f49-a8e0-88a2884ff8e0&metricKeys=accepted_issues%2Cnew_technical_debt%2Cblocker_violations%2Cbugs%2Cclasses%2Ccode_smells%2Ccognitive_complexity%2Ccomment_lines%2Ccomment_lines_density%2Cbranch_coverage%2Cnew_branch_coverage%2Cconditions_to_cover%2Cnew_conditions_to_cover%2Cconfirmed_issues%2Ccoverage%2Cnew_coverage%2Ccritical_violations%2Ccomplexity%2Cduplicated_blocks%2Cnew_duplicated_blocks%2Cduplicated_files%2Cduplicated_lines%2Cduplicated_lines_density%2Cnew_duplicated_lines_density%2Cnew_duplicated_lines%2Ceffort_to_reach_maintainability_rating_a%2Cfalse_positive_issues%2Cfiles%2Cfunctions%2Cgenerated_lines%2Cgenerated_ncloc%2Chigh_impact_accepted_issues%2Cinfo_violations%2Cviolations%2Cprioritized_rule_issues%2Cline_coverage%2Cnew_line_coverage%2Clines%2Cncloc%2Clines_to_cover%2Cnew_lines_to_cover%2Cmaintainability_issues%2Csqale_rating%2Cnew_maintainability_rating%2Cmajor_violations%2Cminor_violations%2Cnew_accepted_issues%2Cnew_blocker_violations%2Cnew_bugs%2Cnew_code_smells%2Cnew_critical_violations%2Cnew_info_violations%2Cnew_violations%2Cnew_lines%2Cnew_maintainability_issues%2Cnew_major_violations%2Cnew_minor_violations%2Cnew_reliability_issues%2Cnew_security_hotspots%2Cnew_security_issues%2Cnew_vulnerabilities%2Copen_issues%2Cprojects%2Calert_status%2Creleasability_rating%2Creliability_issues%2Creliability_rating%2Cnew_reliability_rating%2Creliability_remediation_effort%2Cnew_reliability_remediation_effort%2Creopened_issues%2Csecurity_hotspots%2Csecurity_hotspots_reviewed%2Cnew_security_hotspots_reviewed%2Csecurity_issues%2Csecurity_rating%2Cnew_security_rating%2Csecurity_remediation_effort%2Cnew_security_remediation_effort%2Csecurity_review_rating%2Cnew_security_review_rating%2Cskipped_tests%2Cstatements%2Csqale_index%2Csqale_debt_ratio%2Cnew_sqale_debt_ratio%2Cuncovered_conditions%2Cnew_uncovered_conditions%2Cuncovered_lines%2Cnew_uncovered_lines%2Ctest_execution_time%2Ctest_errors%2Ctest_failures%2Ctest_success_density%2Ctests%2Cvulnerabilities
This stack overflow answer solved my problem (edit the web config file to allow longer)
Whatever you set up the web.config for, that’s what’s in front of the SonarQube server. 
Glad the issue is solved.
This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.