# ServBay & Debugging PHP

**URL:** <https://forums.realmacsoftware.com/t/servbay-debugging-php/47018>\
**Category:** Elements API\
**Created:** [April 1, 2025, 9:49am UTC](https://forums.realmacsoftware.com/t/servbay-debugging-php/47018 "2025-04-01T09:49:49Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![logrunner](https://avatars.discourse-cdn.com/v4/letter/l/59ef9b/32.png) [@logrunner](https://forums.realmacsoftware.com/u/logrunner)\
**Post date:** [April 1, 2025, 9:49am UTC](https://forums.realmacsoftware.com/t/servbay-debugging-php/47018/1 "2025-04-01T09:49:49Z")

</div>

At the [recommendation](https://forums.realmacsoftware.com/t/form-componant-issue-1/46969/3) from @ben I am giving [ServBay](https://www.servbay.com) a try; I normally use Mamp Pro.

I wanted to see if I could use debugging in [PHPStorm](https://www.jetbrains.com/phpstorm/) to be able to single step through PHP code in a published Elements website, while testing my upcoming Elements Blog. Trying to set this up in Mamp Pro looked a bit complicated at first glance. It was relatively easy in ServBay as they have [good documentation](https://support.servbay.com/php/modules/xdebug) on how to do it.

The answer is that it works well. However, initially I was getting a timeout (503 error) after a minute or so from php; not helpful when slowly single-stepping through PHP code. 😉

I found that the answer is to add **request\_terminate\_timeout = 1200** as an additional setting to the PHP config (where 1200 is the number of seconds), see image below:

 ![CleanShot 2025-04-01 at 10.39.38](https://europe1.discourse-cdn.com/flex005/uploads/realmacsoftware1/original/3X/3/4/343c0cea7eb58550603b6b5f20c9c67cc9850e50.png)

I thought I would share just in case any other developer tries using PHPStorm with ServBay or for that matter any other debugger with ServBay. 🙂