On Thu, Jun 26, 2025 at 5:09 PM Barnhart, Steven <[email protected]> wrote:
> Got a little further – I built guacd back with freerdp 3 and everything > works again. I assume it must be some setting or everyone’s RDP would be > broken, right? > > > > --Steve > > > > *From: *Barnhart, Steven <[email protected]> > *Date: *Thursday, June 26, 2025 at 12:52 PM > *To: *'[email protected]' <[email protected]> > *Subject: *Unable to connect to machine via RDP with 1.6.0 > > This is a strange one as I don’t (and just tested again to confirm) this > issue with with at least 1. 6. 0-RC1, but 1. 6. 0 I get a logon failed > almost immediately connecting to most machines, with only this in the log > message for guacd: guacd[1]: > > This is a strange one as I don’t (and just tested again to confirm) this > issue with with at least 1.6.0-RC1, but 1.6.0 I get a logon failed almost > immediately connecting to most machines, with only this in the log message > for guacd: > > > > guacd[1]: INFO: Listening on host 0.0.0.0, port 4822 > > guacd[1]: INFO: Creating new client for protocol "rdp" > > guacd[1]: INFO: Connection ID is "$60ff642d-8ce1-43ae-9f29-9261ed548a72" > > guacd[8]: WARNING: FreeRDP initialization may fail: The current > user's home directory ("/") is not writable, but FreeRDP generally requires > a writable home directory for storage of configuration files and > certificates. > I think you may be running the guacd instances under different accounts, and the one you happen to be using 1.6.0 under does not have write access to the home directory (/, which makes sense - only root would have that). Maybe try a user account that has a real home directory and can write to it? -Nick >
