# Aprol R4.4-01 no login for runtime user

**URL:** <https://community.br-automation.com/t/aprol-r4-4-01-no-login-for-runtime-user/6928>\
**Category:** Other Topics\
**Tags:** aprol\
**Created:** [May 13, 2025, 2:18pm UTC](https://community.br-automation.com/t/aprol-r4-4-01-no-login-for-runtime-user/6928 "2025-05-13T14:18:51Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![Marc\_Mader](https://dub1.discourse-cdn.com/brcommunity/user_avatar/community.br-automation.com/marc_mader/32/1109_2.png) [@Marc\_Mader](https://community.br-automation.com/u/Marc_Mader)\
**Post date:** [May 13, 2025, 2:18pm UTC](https://community.br-automation.com/t/aprol-r4-4-01-no-login-for-runtime-user/6928/1 "2025-05-13T14:18:51Z")

</div>

we installed R4.4-01 to an APC4100, added a runtime system in aprol config, but graphical login to the runtime system is not possible, deactivited for security reasons was the hint from aprolconfig on creation. how can i enable local and vnc login for the runtime system with integrated operator system?

---

<div class="post-metadata">

**Author:** ![F\_Ka](https://avatars.discourse-cdn.com/v4/letter/f/FF8800/32.png) [@F\_Ka](https://community.br-automation.com/u/F_Ka)\
**Post date:** [May 14, 2025, 7:08pm UTC](https://community.br-automation.com/t/aprol-r4-4-01-no-login-for-runtime-user/6928/2 "2025-05-14T19:08:42Z")

</div>

Could you connect successfully via command line (or ssh)?

---

<div class="post-metadata">

**Author:** ![tomas.miculka](https://avatars.discourse-cdn.com/v4/letter/t/FF8800/32.png) [@tomas.miculka](https://community.br-automation.com/u/tomas.miculka)\
**Post date:** [May 15, 2025, 11:50am UTC](https://community.br-automation.com/t/aprol-r4-4-01-no-login-for-runtime-user/6928/3 "2025-05-15T11:50:46Z")

</div>

Hi @Marc_Mader , @F_Ka  
from 4.4-01 is not possible to login dierectly to the runtime for security reasons

 ![image](https://europe1.discourse-cdn.com/brcommunity/original/2X/8/814bc3a64a6b3257d8ed9c1ae66da336111ccadf.png)

---

<div class="post-metadata">

**Author:** ![martin.schmollngrube](https://dub1.discourse-cdn.com/brcommunity/user_avatar/community.br-automation.com/martin.schmollngrube/32/112_2.png) [@martin.schmollngrube](https://community.br-automation.com/u/martin.schmollngrube)\
**Post date:** [May 17, 2025, 11:35am UTC](https://community.br-automation.com/t/aprol-r4-4-01-no-login-for-runtime-user/6928/4 "2025-05-17T11:35:14Z")

</div>

One way would be to adjust the settings for runtime user in /etc/passwd file.

---

<div class="post-metadata">

**Author:** ![system](https://europe1.discourse-cdn.com/brcommunity/original/1X/a202d64f0f03e22a662ed33fbbca6879f1efb794.jpeg) [@system](https://community.br-automation.com/u/system)\
**Post date:** [August 31, 2025, 3:51am UTC](https://community.br-automation.com/t/aprol-r4-4-01-no-login-for-runtime-user/6928/5 "2025-08-31T03:51:43Z")

</div>


