Howdy, Stranger!

It looks like you're new here. If you want to get involved, click one of these buttons!


Shells Virtual Desktop
BMail.ag - Secure Email Service
Server.net
CPLicense.net
VPS Server
Buy VPN
Vultr
VMs for AI
HostDare
ReliableSite White-Label Dedicated Hosting for Resellers
InterServer VPS
BMail.ag - Secure Email Service
Best VPN
High-Performance Bare Metal Server Solutions
Karvl.com
Server Mania Cloud Hosting
DataWagon Hosting
AlphaVPS Hosting
Evoxt.com
Clouvider
VPS Hosting with NVMe
Residential IPs in the US & 4G Mobile Proxies in EU & US with Unlimited Bandwidth
ReliableSite White-Label Dedicated Hosting for Resellers
Rabisu - Hosting Solutions
Shells Virtual Desktop
New on LowEndTalk? Please Register and read our Community Rules.

All new Registrations are manually reviewed and approved, so a short delay after registration may occur before your account becomes active.

rsync not creating folder on remote server

aliletalilet Member
edited January 2025 in Help

I am trying to sync data between local and remote server. But rsync throws following error if the folder being sync'd already doesn't exist on remote.

Permission denied (13)

I am logged in as user user1 on local server from where I am running following command. The folder on local is owned by user user2. If I create the same folder 2023 on remote and make user2 its owner, then the following command works otherwise it doesn't.

rsync -av --delete -e ssh /uploads/2023/ remotevps:/uploads/2023

What's the solution?

Comments

  • Alilet, are saying that you do not see problem with permissions? What cgpt says about this matter when you paste logs?

  • it means the user that is connecting via ssh (for rsync) doesn't have permission to mkdir in /uploads, fix it.

  • Ok I just checked that even if the folder is there, it will not sync files within and will throw same error. Seems like some permission issue. Let me check.

  • @alilet said:
    Ok I just checked that even if the folder is there, it will not sync files within and will throw same error. Seems like some permission issue. Let me check.

    You're in the best position to check permissions, but is "Permission denied (13)" the whole error message?

  • aliletalilet Member
    edited January 2025

    @angstrom said:

    @alilet said:
    Ok I just checked that even if the folder is there, it will not sync files within and will throw same error. Seems like some permission issue. Let me check.

    You're in the best position to check permissions, but is "Permission denied (13)" the whole error message?

    Here is complete message.

    rsync: [generator] recv_generator: mkdir "/uploads/2023" failed: Permission denied (13)
    *** Skipping any contents from this failed directory ***

  • @alilet said:

    @angstrom said:

    @alilet said:
    Ok I just checked that even if the folder is there, it will not sync files within and will throw same error. Seems like some permission issue. Let me check.

    You're in the best position to check permissions, but is "Permission denied (13)" the whole error message?

    Here is complete message.

    rsync: [generator] recv_generator: mkdir "/uploads/2023" failed: Permission denied (13)
    *** Skipping any contents from this failed directory ***

    The user on the remote server doesn't have permission to write to the directory /uploads/2023

  • @angstrom said:

    @alilet said:

    @angstrom said:

    @alilet said:
    Ok I just checked that even if the folder is there, it will not sync files within and will throw same error. Seems like some permission issue. Let me check.

    You're in the best position to check permissions, but is "Permission denied (13)" the whole error message?

    Here is complete message.

    rsync: [generator] recv_generator: mkdir "/uploads/2023" failed: Permission denied (13)
    *** Skipping any contents from this failed directory ***

    The user on the remote server doesn't have permission to write to the directory /uploads/2023

    Yeah this was the issue. I used chown to assign permission to that user1 but kept group user2 and now it is working.

Sign In or Register to comment.