curlftpfs doesn't work for a username with a “@”
My hosting company makes all my usernames with a "@" in them.
curlftpfs user="user@domain.com:pass" ftp://ftp.domain.com/ ~/domain/
For some reason I get in response
Error connecting to ftp: Couldn't
resolve host 'domain.com:pass'
I think that it's trying to connect to user@domain.com without the password
(because of the @ sign)
ftp curl curlftpfs
edited Apr 10 '11 at 11:25
Sebastian Paaske Tørholm
3,98031825
asked Apr 10 '11 at 11:07
AsafAsaf
51411025
add a comment |
My hosting company makes all my usernames with a "@" in them.
curlftpfs user="user@domain.com:pass" ftp://ftp.domain.com/ ~/domain/
For some reason I get in response
Error connecting to ftp: Couldn't
resolve host 'domain.com:pass'
I think that it's trying to connect to user@domain.com without the password
(because of the @ sign)
ftp curl curlftpfs
edited Apr 10 '11 at 11:25
Sebastian Paaske Tørholm
3,98031825
asked Apr 10 '11 at 11:07
AsafAsaf
51411025
add a comment |
My hosting company makes all my usernames with a "@" in them.
curlftpfs user="user@domain.com:pass" ftp://ftp.domain.com/ ~/domain/
For some reason I get in response
Error connecting to ftp: Couldn't
resolve host 'domain.com:pass'
I think that it's trying to connect to user@domain.com without the password
(because of the @ sign)
ftp curl curlftpfs
edited Apr 10 '11 at 11:25
Sebastian Paaske Tørholm
3,98031825
asked Apr 10 '11 at 11:07
AsafAsaf
51411025
My hosting company makes all my usernames with a "@" in them.
curlftpfs user="user@domain.com:pass" ftp://ftp.domain.com/ ~/domain/
For some reason I get in response
Error connecting to ftp: Couldn't
resolve host 'domain.com:pass'
I think that it's trying to connect to user@domain.com without the password
(because of the @ sign)
ftp curl curlftpfs
ftp curl curlftpfs
edited Apr 10 '11 at 11:25
Sebastian Paaske Tørholm
3,98031825
asked Apr 10 '11 at 11:07
AsafAsaf
51411025
edited Apr 10 '11 at 11:25
Sebastian Paaske Tørholm
3,98031825
asked Apr 10 '11 at 11:07
AsafAsaf
51411025
edited Apr 10 '11 at 11:25
Sebastian Paaske Tørholm
3,98031825
edited Apr 10 '11 at 11:25
Sebastian Paaske Tørholm
3,98031825
edited Apr 10 '11 at 11:25
Sebastian Paaske Tørholm
3,98031825
3,98031825
asked Apr 10 '11 at 11:07
AsafAsaf
51411025
asked Apr 10 '11 at 11:07
AsafAsaf
51411025
asked Apr 10 '11 at 11:07
AsafAsaf
51411025
51411025
add a comment |
add a comment |
2 Answers
2
active
oldest
votes
cURL is interpreting everything after the first @ sign as the domain to connect to. What you need to do is either fool cURL into working without the first @ sign, or find some other way of telling CurlFtpFS your username.
The former may possibly be done by replacing the @ with the URL encoded %40 - it may or may not work - try it and see.
The other way can be to see if there is a --username or --user parameter to CurlFtpFS that can be used instead of including it in the URL. I am not familiar enough with CurlFtpFS to know if there is or not off hand. The manual pages should tell you if there is or not.
edited Aug 23 '11 at 6:48
3498DB
15.7k114762
answered Apr 10 '11 at 11:11
MajenkoMajenko
27.1k34472
holy crap, I did this command sudo curlftpfs -o allow_other user%40domain.com:pass@domain.com ~/domain/ And now for some reason I can't do an "ls" on my home directory!
– Asaf
Apr 10 '11 at 11:44
2
@Asaf: When you runls, it calls stat() on each item in the directory; when it reaches~/domain, it has to wait until curlftpfs responds. (For this problem, I usually put all remote mountpoints in a separate directory, such as~/fs/or~/mnt/.) Since curlftpfs is FUSE-based, you can kill its process if it hangs for too long.
– grawity
Apr 10 '11 at 13:19
add a comment |
I'm wondering if you are missing the -o switch, so that your example above of:
curlftpfs user="user@domain.com:pass" ftp://ftp.domain.com/ ~/domain/
should be:
curlftpfs -o user="user@domain.com:pass" ftp://ftp.domain.com/ ~/domain/
Does that work?
answered Apr 10 '11 at 11:26
3498DB3498DB
15.7k114762
add a comment |
Your Answer
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "3"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsuperuser.com%2fquestions%2f269006%2fcurlftpfs-doesnt-work-for-a-username-with-a%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
2 Answers
2
active
oldest
votes
2 Answers
2
active
oldest
votes
active
oldest
votes
active
oldest
votes
cURL is interpreting everything after the first @ sign as the domain to connect to. What you need to do is either fool cURL into working without the first @ sign, or find some other way of telling CurlFtpFS your username.
The former may possibly be done by replacing the @ with the URL encoded %40 - it may or may not work - try it and see.
The other way can be to see if there is a --username or --user parameter to CurlFtpFS that can be used instead of including it in the URL. I am not familiar enough with CurlFtpFS to know if there is or not off hand. The manual pages should tell you if there is or not.
edited Aug 23 '11 at 6:48
3498DB
15.7k114762
answered Apr 10 '11 at 11:11
MajenkoMajenko
27.1k34472
holy crap, I did this command sudo curlftpfs -o allow_other user%40domain.com:pass@domain.com ~/domain/ And now for some reason I can't do an "ls" on my home directory!
– Asaf
Apr 10 '11 at 11:44
2
@Asaf: When you runls, it calls stat() on each item in the directory; when it reaches~/domain, it has to wait until curlftpfs responds. (For this problem, I usually put all remote mountpoints in a separate directory, such as~/fs/or~/mnt/.) Since curlftpfs is FUSE-based, you can kill its process if it hangs for too long.
– grawity
Apr 10 '11 at 13:19
add a comment |
cURL is interpreting everything after the first @ sign as the domain to connect to. What you need to do is either fool cURL into working without the first @ sign, or find some other way of telling CurlFtpFS your username.
The former may possibly be done by replacing the @ with the URL encoded %40 - it may or may not work - try it and see.
The other way can be to see if there is a --username or --user parameter to CurlFtpFS that can be used instead of including it in the URL. I am not familiar enough with CurlFtpFS to know if there is or not off hand. The manual pages should tell you if there is or not.
edited Aug 23 '11 at 6:48
3498DB
15.7k114762
answered Apr 10 '11 at 11:11
MajenkoMajenko
27.1k34472
holy crap, I did this command sudo curlftpfs -o allow_other user%40domain.com:pass@domain.com ~/domain/ And now for some reason I can't do an "ls" on my home directory!
– Asaf
Apr 10 '11 at 11:44
2
@Asaf: When you runls, it calls stat() on each item in the directory; when it reaches~/domain, it has to wait until curlftpfs responds. (For this problem, I usually put all remote mountpoints in a separate directory, such as~/fs/or~/mnt/.) Since curlftpfs is FUSE-based, you can kill its process if it hangs for too long.
– grawity
Apr 10 '11 at 13:19
add a comment |
cURL is interpreting everything after the first @ sign as the domain to connect to. What you need to do is either fool cURL into working without the first @ sign, or find some other way of telling CurlFtpFS your username.
The former may possibly be done by replacing the @ with the URL encoded %40 - it may or may not work - try it and see.
The other way can be to see if there is a --username or --user parameter to CurlFtpFS that can be used instead of including it in the URL. I am not familiar enough with CurlFtpFS to know if there is or not off hand. The manual pages should tell you if there is or not.
edited Aug 23 '11 at 6:48
3498DB
15.7k114762
answered Apr 10 '11 at 11:11
MajenkoMajenko
27.1k34472
cURL is interpreting everything after the first @ sign as the domain to connect to. What you need to do is either fool cURL into working without the first @ sign, or find some other way of telling CurlFtpFS your username.
The former may possibly be done by replacing the @ with the URL encoded %40 - it may or may not work - try it and see.
The other way can be to see if there is a --username or --user parameter to CurlFtpFS that can be used instead of including it in the URL. I am not familiar enough with CurlFtpFS to know if there is or not off hand. The manual pages should tell you if there is or not.
edited Aug 23 '11 at 6:48
3498DB
15.7k114762
answered Apr 10 '11 at 11:11
MajenkoMajenko
27.1k34472
edited Aug 23 '11 at 6:48
3498DB
15.7k114762
edited Aug 23 '11 at 6:48
3498DB
15.7k114762
edited Aug 23 '11 at 6:48
3498DB
15.7k114762
15.7k114762
answered Apr 10 '11 at 11:11
MajenkoMajenko
27.1k34472
answered Apr 10 '11 at 11:11
MajenkoMajenko
27.1k34472
answered Apr 10 '11 at 11:11
MajenkoMajenko
27.1k34472
27.1k34472
holy crap, I did this command sudo curlftpfs -o allow_other user%40domain.com:pass@domain.com ~/domain/ And now for some reason I can't do an "ls" on my home directory!
– Asaf
Apr 10 '11 at 11:44
2
@Asaf: When you runls, it calls stat() on each item in the directory; when it reaches~/domain, it has to wait until curlftpfs responds. (For this problem, I usually put all remote mountpoints in a separate directory, such as~/fs/or~/mnt/.) Since curlftpfs is FUSE-based, you can kill its process if it hangs for too long.
– grawity
Apr 10 '11 at 13:19
add a comment |
holy crap, I did this command sudo curlftpfs -o allow_other user%40domain.com:pass@domain.com ~/domain/ And now for some reason I can't do an "ls" on my home directory!
– Asaf
Apr 10 '11 at 11:44
2
@Asaf: When you runls, it calls stat() on each item in the directory; when it reaches~/domain, it has to wait until curlftpfs responds. (For this problem, I usually put all remote mountpoints in a separate directory, such as~/fs/or~/mnt/.) Since curlftpfs is FUSE-based, you can kill its process if it hangs for too long.
– grawity
Apr 10 '11 at 13:19
holy crap, I did this command sudo curlftpfs -o allow_other user%40domain.com:pass@domain.com ~/domain/ And now for some reason I can't do an "ls" on my home directory!
– Asaf
Apr 10 '11 at 11:44
holy crap, I did this command sudo curlftpfs -o allow_other user%40domain.com:pass@domain.com ~/domain/ And now for some reason I can't do an "ls" on my home directory!
– Asaf
Apr 10 '11 at 11:44
2
2
@Asaf: When you run
ls, it calls stat() on each item in the directory; when it reaches ~/domain, it has to wait until curlftpfs responds. (For this problem, I usually put all remote mountpoints in a separate directory, such as ~/fs/ or ~/mnt/.) Since curlftpfs is FUSE-based, you can kill its process if it hangs for too long.– grawity
Apr 10 '11 at 13:19
@Asaf: When you run
ls, it calls stat() on each item in the directory; when it reaches ~/domain, it has to wait until curlftpfs responds. (For this problem, I usually put all remote mountpoints in a separate directory, such as ~/fs/ or ~/mnt/.) Since curlftpfs is FUSE-based, you can kill its process if it hangs for too long.– grawity
Apr 10 '11 at 13:19
add a comment |
I'm wondering if you are missing the -o switch, so that your example above of:
curlftpfs user="user@domain.com:pass" ftp://ftp.domain.com/ ~/domain/
should be:
curlftpfs -o user="user@domain.com:pass" ftp://ftp.domain.com/ ~/domain/
Does that work?
answered Apr 10 '11 at 11:26
3498DB3498DB
15.7k114762
add a comment |
I'm wondering if you are missing the -o switch, so that your example above of:
curlftpfs user="user@domain.com:pass" ftp://ftp.domain.com/ ~/domain/
should be:
curlftpfs -o user="user@domain.com:pass" ftp://ftp.domain.com/ ~/domain/
Does that work?
answered Apr 10 '11 at 11:26
3498DB3498DB
15.7k114762
add a comment |
I'm wondering if you are missing the -o switch, so that your example above of:
curlftpfs user="user@domain.com:pass" ftp://ftp.domain.com/ ~/domain/
should be:
curlftpfs -o user="user@domain.com:pass" ftp://ftp.domain.com/ ~/domain/
Does that work?
answered Apr 10 '11 at 11:26
3498DB3498DB
15.7k114762
I'm wondering if you are missing the -o switch, so that your example above of:
curlftpfs user="user@domain.com:pass" ftp://ftp.domain.com/ ~/domain/
should be:
curlftpfs -o user="user@domain.com:pass" ftp://ftp.domain.com/ ~/domain/
Does that work?
answered Apr 10 '11 at 11:26
3498DB3498DB
15.7k114762
answered Apr 10 '11 at 11:26
3498DB3498DB
15.7k114762
answered Apr 10 '11 at 11:26
3498DB3498DB
15.7k114762
answered Apr 10 '11 at 11:26
3498DB3498DB
15.7k114762
15.7k114762
add a comment |
add a comment |
Thanks for contributing an answer to Super User!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsuperuser.com%2fquestions%2f269006%2fcurlftpfs-doesnt-work-for-a-username-with-a%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
