# ekosdebugger for remote system - CLI only

**URL:** <https://forum.indilib.org/t/ekosdebugger-for-remote-system-cli-only/13515>\
**Category:** General\
**Created:** [May 29, 2025, 6:26am UTC](https://forum.indilib.org/t/ekosdebugger-for-remote-system-cli-only/13515 "2025-05-29T06:26:59Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![nyx](https://forum.indilib.org/letter_avatar_proxy/v4/letter/n/dc4da7/32.png) [@nyx](https://forum.indilib.org/u/nyx)\
**Post date:** [May 29, 2025, 6:26am UTC](https://forum.indilib.org/t/ekosdebugger-for-remote-system-cli-only/13515/1 "2025-05-29T06:26:59Z")

</div>

I decided to continue my [other topic](https://indilib.org/forum/general/15478-considerations-before-switching-to-ekos-indilib.html) here, since every time I try to post something there I’m instantly getting logged out.

Anyway, I’d like to use ekosdebugger to debug the indi\_dragonfly\_dome driver, but it is a remote system with no GUI.

Since ekosdebugger seems to be running local only and requires GUI, is there any way to debug using the indiserver on the remote system?