Access Denied saving configuration.yaml using winscp

Total noob here. I have installed HA on ubuntu using the virtualenv method listed in the getting started section. For the life of me, i can’t save the file. I have changed the file protocol to SCP and i have changed the shell to sudo su as directed in the two threads that address the topic. Do i have to make a hass user and password? What could i be doing wrong?

Your noobian friend,

lord humongous

Sorry I’m not in front of my comp right now but have a look at the settings in the winscp session that you configure

They’re is a setting where you can specify that you want sudo enabled

Let me know if you find it or I’ll check when I get back home and post it here

updated : I’ll copy my configuration here later on as it works perfectly for me :slight_smile:

Hang on :wink:

here you go

Thanks! I can try it in a bit and let you know.

The settings are exact and still getting permission errors. When using sudo su- i dont get an error but it does not connect…it refers back to the login page with no access. Here comes the stupid question…when using sudo su, what should my user name be. I have a hass user but dont remember setting up a user name and password. Is there any other ways to set permissions?

Pay attention to use SCP and not SFTP.

Am i understanding that Winscp cannot even connect ?

If it’s the case, make sure that this screen is the configured properly as well

I am able to connect no problem. But it wont let me save the configuration.yaml file. Permission denied.

Using WinSCP, if you highlight the file and choose properties, does it look like this?

My configuration.yaml file is located in /home/hass/.homeassistant.

It differs from the screen shot listed above as it looks like the configuration.yaml file there is located at /home/hass.

My screen the default setting for the group setting is nogroup. There is no root option in the drop down menu.
My only Owner option is hass.

When i open the .homeassistant properties under /home/hass/ i do have the option to put group=root and owner=root and click the permission like the above referenced screen i receive the following:

“Cannot change properties of file .homeassistant”

Command 'chgrp “root” “.homeassistant” failed with return code 1 and error message chgrp: changing group of .homeassistant: Operation not permitted.

And if someone would kindly show my noobian ass how to screen shot i would show you!

Could i have “mucked up” permissions like the guidance documentation described…how can i fix this?

Are you able to access it directly from your Ubuntu computer?

To take screen shots very simply from Windows you can use snippets which allows you to select the area to capture. If you click the start menu and start typing Snipping Tool you should be able to launch it. Otherwise it’s under Windows Accessories.

Now since you are using ubuntu there probably is no reason you would have a pi account to log in with?, you might need to use another existing account or create one. How did you install Hass? Did you use putty? Perhaps use the same method to issue a permissions edit first…

$ sudo chmod 777 /home/hass/.homeassistant/configuration.yaml

Thanks in advance for your help. The permission change did not seem to work. Another noobian type question. With the permission change, what should the user name be. I have my ubuntu user name and password and i also have a hass user but i dont recall setting a password. I can get into root after entering through ubuntu with a set password. Any ideas?

Use that account.

but this will create a security flaw, it will work but you better create a user for your home assistant user and use this user to create and execute the file

if you will not but your home assistant visible to the world (on internet) then @BarryHampants is right, you can use root

I have hass as user, but no permissions. How do i create another user? Remember…total noob. In what direction do i beed to go?

Sorry for the confusion, I have misinterpreted the question.

I just meant for you to log in and use that user to change the permissions on your config file one time so you can edit it.