# Issue with api/rules/search when trying to run analysis through VS

**URL:** <https://community.sonarsource.com/t/issue-with-api-rules-search-when-trying-to-run-analysis-through-vs/128324>\
**Category:** SonarQube Server / Community Build\
**Tags:** api, scanner\
**Created:** [October 17, 2024, 3:33pm UTC](https://community.sonarsource.com/t/issue-with-api-rules-search-when-trying-to-run-analysis-through-vs/128324 "2024-10-17T15:33:06Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![thomas.weaver](https://avatars.discourse-cdn.com/v4/letter/t/d2c977/32.png) [@thomas.weaver](https://community.sonarsource.com/u/thomas.weaver)\
**Post date:** [October 17, 2024, 3:33pm UTC](https://community.sonarsource.com/t/issue-with-api-rules-search-when-trying-to-run-analysis-through-vs/128324/1 "2024-10-17T15:33:06Z")

</div>

I am trying to run a scan on a .Net Core project i have been working on. When i ran the first scan it worked as expected and a report was created however after i made some changes and attempted to run the process again using the same commands, it fails sonarscanner begin step due to the api/rules/search call being made by the api. It runs using the following:  
api/rules/search?f=repo,name,severity,lang,internalKey,templateKey,params,actives&ps=500&qprofile=AYR\_vkccJyECsrxRrY8v&p=1

And returns a Error 502. If i alter the URL in a browser to remove the ps=500 or change it to be a lower value like 100 it will return the response.

Is it possible to change this anywhere in the SonarQube configuration / interface to either remove the ps=500 or edit the figuire as at the moment i cannot run scans?

---

<div class="post-metadata">

**Author:** ![ganncamp](https://dub1.discourse-cdn.com/sonarsource/user_avatar/community.sonarsource.com/ganncamp/32/1261_2.png) [@ganncamp](https://community.sonarsource.com/u/ganncamp)\
**Post date:** [October 18, 2024, 3:11pm UTC](https://community.sonarsource.com/t/issue-with-api-rules-search-when-trying-to-run-analysis-through-vs/128324/2 "2024-10-18T15:11:31Z")

</div>

Hi,

Welcome to the community!

> [@thomas.weaver](#):
>
> however after i made some changes and attempted to run the process again

To be clear, these were code changes, not pipeline changes, right? 😅

> [@thomas.weaver](#):
>
> And returns a Error 502.

What do your [server logs](https://docs.sonarqube.org/latest/setup/troubleshooting/) say?

&nbsp;  
Ann

---

<div class="post-metadata">

**Author:** ![thomas.weaver](https://avatars.discourse-cdn.com/v4/letter/t/d2c977/32.png) [@thomas.weaver](https://community.sonarsource.com/u/thomas.weaver)\
**Post date:** [October 18, 2024, 3:47pm UTC](https://community.sonarsource.com/t/issue-with-api-rules-search-when-trying-to-run-analysis-through-vs/128324/3 "2024-10-18T15:47:21Z")

</div>

Hi Ann,

The changes were code changes made after reviewing the scan results from the first run. We didn’t make any changes to the pipeline.

We have reviewed the servers but it doesn’t make any reference to the 502 error we are recieving as it is saying the process is timing out when we try to run the command through the terminal in VS / attempt to access the URL through the browser. If we access the site through the localhost:90000 in the server where our instance is hosted, it will load the contents of the query

---

<div class="post-metadata">

**Author:** ![ganncamp](https://dub1.discourse-cdn.com/sonarsource/user_avatar/community.sonarsource.com/ganncamp/32/1261_2.png) [@ganncamp](https://community.sonarsource.com/u/ganncamp)\
**Post date:** [October 18, 2024, 3:50pm UTC](https://community.sonarsource.com/t/issue-with-api-rules-search-when-trying-to-run-analysis-through-vs/128324/4 "2024-10-18T15:50:38Z")

</div>

Hi,

> [@thomas.weaver](#):
>
> doesn’t make any reference to the 502

> [@thomas.weaver](#):
>
> the process is timing out when we try to run the command through the terminal in VS / attempt to access the URL through the browser.

This has all the hallmarks of something “helpful” on the network. I think you should talk to your network folks.

&nbsp;  
HTH,  
Ann