No write permision to edit echolink.conf

Archive
1

I can copy files (SFTP (FileZilla)) from "/etc/asterisk/echolink.conf"

But i don't have any rights to copy it back after editing or to edit the file itself or any other file in the "asterisk" directory.

error writing /etc/asterisk/echolink.conf: Permission denied

Any help is welcome, i'm near to giving up.

Thanks, Gary

2

I don't belive you can sudo with FileZilla to be able to edit files in that folder since that folder is restricted to root access.

You can use this example to launch the terminal shell:

Terminal / Console - AllStarLink Manual

and edit the file directly with "nano". E.g.:

sudo nano /etc/asterisk/echolink.conf

3

Thanks for your quick reply,
I feel very stupid, as I wasn't using the "sudo" command.
Ive been puzzling for days with this and now Ive got it edited.
Thank you very much,
Haven't got Echolink to work just yet, but this is progress.

Thanks
Gary

4

Eventually got everything up and running.
Very satisfying.

Gary

5

Gary, if you want to use filezilla to write to your files. Enable root login and then login as root and do what you wish with filezilla. from the terminal nano /etc/ssh/sshd_config about 25 lines down there's a line that says #permitrootlogin password-prohibited remove the leading # and make the line read permitrootlogin yes ctrl+x Y to save back at the root prompt service ssh restart. then you'll be able to login as root using your root password with filezilla and make your edits.

1 Like
6

Ah, the missing link...
You see everyone online using Filezilla or WinSCP but nobody tells you how to enable the root access, until now...
I'm definitely going to do that, it'l make things a lot easier.

Thanks a lot

7

Just remember, running filezilla/winscp as root, when you create a new file like for a shell script, it will be owned by root unless you change the ownership.

That would prevent asterisk from making a call to it.
Scripts running by/through asterisk should be
asterisk:asterisk with appropriate r/w ability

Editing an existing file on the server should not change anything.

8

Just keep in mind that ssh-as-root is disabled for a reason. By enabling it, especially using passwords, you are creating a serious cyber security risk. If your servers have inbound internet access to SSH, please do not enable root logins.

9

Thanks for all the advise

10

This topic was automatically closed 3 days after the last reply. New replies are no longer allowed.