Dreamweaver FTP Can't Connect
As I've mentioned before, Dreamweaver's FTP works fantastically well. No need to switch to another FTP program to FTP files that you're already looking at in DW's tree view.* Except that, in some circumstances, DW simply will not connect to the server, no matter that you've followed all the usual instructions.
Thanks to Craig Lido for pointing me to Macromedia's Dreamweaver TechNote:
Add a colon and the port number to the end of the FTP host name in the FTP Host text box. The FTP host name will appear similarly to the following examples:
-www.myhost.com:80
-123.456.789.012:80
Much appreciated.
82 Comments to "Dreamweaver FTP Can't Connect"
Have your say ...
If this is your first comment, it will be held for moderation (but comments are appreciated). Otherwise, just be courteous, don't drop links unless highly pertinent — and no substituting keywords for your name. Posters must be 16 or older. We use Akismet, so if you don't see your non-spam comment posted, contact me.
Becky Bohman says:
Comment posted on 02/23/09 @ 2:10 pm
I just switched hosting companies and am having difficulties connecting to the server through Dreamweaver. I have ALWAYS used Dreamweaver for coding, designing, uploading, etc. but for some reason with this new server, it absolutely will not accept my username and password. I've connected using FileZilla just fine using the same login info, but for some reason Dreamweaver is being stubborn. Any ideas please?
Diane Vigil says:
Comment posted on 02/23/09 @ 2:17 pm
A few things to try:
- make sure you're using the correct username and password
- are you
- try the tips in my article above
- In Sites > Manage Sites > Edit > Remote Info, deselect "Use Secure FTP (SFTP)
One of those ought to do it. Let me know what happens.
moira says:
Comment posted on 03/16/09 @ 10:05 pm
I have been using an old version – Dreamweaver 2 – which has been great – and now I am having ftp problems. I have tried all of the above and I still get a message – host found connecting – and then – an ftp error occurred – connect make connection to host.
I have rung mine host and want me to use their Zilla thing as well which I have to buy. Why would I when D/W has been perfect. Hope you can help.
Cheers Moira
Diane Vigil says:
Comment posted on 03/17/09 @ 12:43 am
A couple of questions: have you switched hosts recently? If not, have they changed something? Are you trying to upload via a secure connection (SFTP) that's being rejected?
You can always try Filezilla, which is free. If nothing else, that may give you some clues.
Thing is, I'm not sure whether FTP protocols may have changed. I used WS_FTP '95 for years before upgrading, and then using DW's internal FTP functions. So I'm not sure whether there may be something different with respect to FTP functions this much later on.
Joshua Solomon says:
Comment posted on 03/17/09 @ 6:54 pm
I was having the same issue with Dreamweaver not connecting to my site via ftp while Filezilla was having no problems. Here's what I did:
Go into: Manage Sites
Select Your Site
Click Edit
Select the Advanced Tab
Select Remote Info from the list on the left.
Then in the ftp host enter:
yourdomain.com:21
or
your Static IP address followed by :21
ex. 192.168.0.1:21
NOW HERE IS THE KEY!! Change the FTP Time Out setting
Click the button that says "Firewall Settings"
Find "FTP time out:"
Replace the 2 Seconds with 10 Seconds.
Then try it if it still doesn't work check the "Use passive FTP" check box and try again.
Diane Vigil says:
Comment posted on 03/17/09 @ 7:03 pm
Port number 21? Interesting; mine's already set for port 21 in the firewall settings, but not in the host name.
Thanks, Joshua.
john says:
Comment posted on 05/8/09 @ 3:08 pm
i had the same prob. filezilla connects but not DW. i only changed my timeout, under "firewall settings" from 10 secs to 60 secs and that fixed it.
Diane Vigil says:
Comment posted on 05/12/09 @ 1:17 am
Excellent. Great tip, John.
Steve Douglas says:
Comment posted on 05/29/09 @ 11:07 am
Thank you thank you thank you! Adding the colon and the port made DW CS3 immediately connect! I'd been getting the dorky error dialogs for over an hour until I found this site and your suggestion.
Thanks again!
Janell says:
Comment posted on 07/23/09 @ 8:56 am
I've been using dreamweaver (MX2004) for over 2 years now with absolutely no problems connecting to the ftp. Within the last 3 days, it's gone to hell; and nothing will connect – I get the "failed to connect to server" or "server unavailable/not accepting new connections" and occasionally the "timed out" error. I'm curious if it's a server issue, as I've tried connecting from a different FTP program with no luck as well (although it still works occasionally more often than DW does); but according to my host, nothing of the sort is going on with them.
I've tried all of the above tricks and gotten nowhere. Considering this is my business website, I'm more than a bit peeved. Any ideas?
Diane Vigil says:
Comment posted on 07/23/09 @ 2:48 pm
That's odd, if another FTP program also can't connect to the server. I have occasionally had a problem uploading PDF files with DW (in which case I upload them with WS_FTP), but that's about it.
What types of files are you trying to upload?
Otherwise, if it's not something along these lines, I'd guess that it may be a server issue — but, in any case, it's hardly convenient not to be able to update your business website.
Bob says:
Comment posted on 08/25/09 @ 10:29 am
Woohoo "Use passive ftp fixed an issue a customer of our ISP was having – TY
Diane Vigil says:
Comment posted on 08/25/09 @ 10:39 am
Excellent! Glad it helped.
Fred says:
Comment posted on 10/6/09 @ 6:06 am
I have tried all of your suggestions. Still no connection. Anything else I can try? Outside of re-installing.
Diane Vigil says:
Comment posted on 10/6/09 @ 6:14 am
I'm not sure that reinstalling will help; if Dreamweaver is working otherwise but you can't FTP to the server, that's where the error lies.
If you've tried all the other suggestions, one thing I'd suggest would be to contact your web host. For instance, it may be that your host has specified something else than :80:
-www.myhost.com:80
-123.456.789.012:80
Something else I recently encountered: a new server was configured a little differently than "normal" and I, of course, was trying different methods of connecting via Dreamweaver (click, click, click in rapid succession) … so the server ended up blocking me! LOL. At any rate, the upline web host sorted it out and all is fine.
Let me know how it goes.
Fred says:
Comment posted on 10/7/09 @ 5:36 am
Hey Diane,
Contacted my host. Tried the port. It didn't work.
It's so frustrating. :(
Thanks,
Fred
Diane Vigil says:
Comment posted on 10/7/09 @ 5:40 am
Okay. Let's start here: who is your web host?
omar says:
Comment posted on 11/4/09 @ 3:21 pm
im having the same problem and im with godaddy
Diane Vigil says:
Comment posted on 11/4/09 @ 3:31 pm
Okay. In Dreamweaver, in the Site definition (in the Advanced tab), the HTTP address should be something like this:
http://yoursite.com/public_html/
or http://yoursite.com/www/
or http://yoursite.com/htdocs/
Normally, you can find this info simply by FTPing in to your web hosting account.
The thing with GoDaddy is finding your actual server path, which isn't obvious when you FTP in. Let's say your username is xyz444. Your server path for Dreamweaver might be:
http://yoursite.com/home/content/x/y/z/html/
-or-
http://yoursite.com/home/content/x/y/z/maybesomenumbers/html/
If you don't have this information, call GoDaddy. Ignore any advice they give you that the problem is your "web designer" or "Dreamweaver". If you get the right info, the above should work.
Unfortunately, not all the GoDaddy tech support folks are aware of the above.
Phil says:
Comment posted on 11/18/09 @ 6:45 pm
OMG I\'m so new at this. I was entering the site as ftp://mydomain.com
I changed it to mydomain.com:21 and that fixed it. I figured I would put that out there in case someone else made that mistake.
Adrian Guerra II says:
Comment posted on 01/15/10 @ 9:39 am
Copy the actual IP address with port number (ex. 192.22.33.01:21) fixed the problem for me. It seems as though Dreamweaver is not changing the domain name to the ip address after submitting for test.
Chris says:
Comment posted on 01/27/10 @ 8:59 am
Ok for a few people out there I tried absolutely everything and the only thing that worked was to use the ip address instead of the ftp server name http://ftp.mysite.com for example.
I am on Mac OSX 10.5 using Dreamweaver CS4. It seems to be a bug. I could connect to all my servers via my other ftp client and some servers using DWCS4 but not ones that all began with the same server name. Anything that was http://ftp.mysite.com for example would not connect.
Like Adrian it appears the ftp address was not getting converted to an IP address.
Chris says:
Comment posted on 01/27/10 @ 9:01 am
Note to moderator please remove above urls in my post as one links to a real ftp area. My bad :/
Diane Vigil says:
Comment posted on 01/27/10 @ 12:54 pm
I switched it to "mysite.com".
enolam says:
Comment posted on 01/27/10 @ 2:55 pm
thank you all / close to pulling my hair out
Anshul says:
Comment posted on 03/28/10 @ 12:11 pm
Thanks a lot guys! Switching to using passive ftp solved my problem.
Cheers !!
Diane Vigil says:
Comment posted on 03/28/10 @ 12:14 pm
You're welcome, Anshul. Glad it helped. :)
Gdub says:
Comment posted on 04/15/10 @ 8:17 pm
Passive FTP worked for me – excellent tip after searching online for about 30 minutes. Also added yourdomain.com:21
Thanks again.
Diane Vigil says:
Comment posted on 04/16/10 @ 1:08 am
Cool. Glad it helped. :)
Michael says:
Comment posted on 05/18/10 @ 8:02 am
I could not get dreamweaver to connect to host no matter what!
I solved the problem by converting my 'FTP Host Address' to an 'IP address' (i.e. what was 'ftp.blahblah.com' is now '208.285.144.12′).
You can convert your Host address to an IP easily using this website:
http://www.hcidata.info/host2ip.htm
Brilliant! Thanks to Adrian and Chris above!
Diane Vigil says:
Comment posted on 05/18/10 @ 8:20 am
Good point, Michael. I've often used IP addresses for FTP host purposes.
Not sure (not enough coffee yet) how that would work if the website is on a shared IP. It's *possible* that it would work based on the username/password combination.
stephanie says:
Comment posted on 07/15/10 @ 3:26 pm
I have a problem similar to what is posted here. Any help is badly needed.
I use DWMX2004 on a G5 Mac using OSX10.5.8.
Working great no problems at all. Then all of a sudden FTP won't connect. To any servers, godaddy, yahoo, none.
I do not have a router or any type firewall, nothing has changed on my computer, noting downloaded or added, nothing at all
I have tried every type fix above and then some all I get is "An FTP error occurred – cannot make connection to host. The server is not responding."
Oddly the error comes up immediately, it doesn't go thru the "trying to connect" progress bar. Its like it doesn't even try, just errors immediately.
I took my DWMX2004 install disk to my friends house he kindly let me install it on his mac computer (fresh) and it connected perfectly.
So something in my dreamweaver operating files corrupt and not attempting FTP or something blocking it?
But what would cause this? I have scanned for viruses, etc. finding nothing.
I have no idea where to even start looking. I maybe need to uninstall DWMX2004 from my computer but not sure how to get it all out so I can install it fresh, maybe that will do it.
thank you very much any help is appreciated i am pulling my hair out!
Diane Vigil says:
Comment posted on 07/15/10 @ 4:45 pm
Okay. This is a nice puzzle. :)
When you say "all of a sudden FTP won't connect", do you mean Dreamweaver's FTP, or any FTP? Have you tried connecting to a server with another FTP program?
If another FTP program will connect, but DW won't, then it sounds like a reinstall may be the answer.
CGR says:
Comment posted on 07/22/10 @ 5:13 am
Just had this with Dreamweaver MX, it was strange because it's worked fine with the configuration since it was installed, I was even able to test the ftp settings.
However I do have to enter in /httpdocs/ in the host directory, not sure if that affects in any way?
Couldn't upload a file, but I was able to browse to the remote view of the site, when I browsed back to the local view it worked again.
Although lately I have been getting a problem with Dreamweaver losing my FTP username/logon
Time to upgrade to the latest version methinks!
Diane Vigil says:
Comment posted on 07/22/10 @ 6:08 am
Hi CGR,
You can save your Site settings:
Site > Manage Sites > Export
Then save it somewhere. When it drops out, just do:
Site > Manage Sites > Import
As to why your DWMX suddenly couldn't connect — was it to a server/website where it had previously worked?
And, yes, you'd have to put in /httpdocs (without the last slash). Otherwise, you may find yourself uploading to the directory above the website root directory.
Another thing that could be weird is that perhaps you tried to upload and overwrite a file that had been uploaded by root (in which case it wouldn't work). Or perhaps it was a temporary server glitch, or a temporary lapse in your Internet connectivity. Hard to say without knowing more.
AR says:
Comment posted on 08/4/10 @ 10:03 am
I have just bumped into the same problem. Thought it might have been something to do with my system so did system restore and it's still giving me same error. But it works perfectly fine with FileZila
I've tried doing everything suggested in this discussion so far : checking username/password, converting to IP address and adding relative port number, switching passive ftp and SFTP but no luck at all.
Since I've just switched to new host, I've just opened support ticket with them hoping to solve this issue because it is truly annoying.
Diane Vigil says:
Comment posted on 08/4/10 @ 11:01 am
Who's the web host? For one, GoDaddy requires special setups; see Comment #19.
AR says:
Comment posted on 08/4/10 @ 2:34 pm
I have just switched to Host Media UK last week.
Just tried the comment #19 way by adding the extensions but it doesn't seem to go anywhere. One thing I've noticed is that when I test it using my site's IP address and Port number it then gives me another error saying "Dreamweaver could not connect because the server is down or not accepting connection"
Diane Vigil says:
Comment posted on 08/4/10 @ 2:37 pm
Okay. Comment #19 was for GoDaddy hosting. I would check with your web host, as there may be something different about the FTP setup. But the "server is down or not accepting connection" does not sound good.
I saw that you tried passive FTP and SFTP. Since that didn't work, I'd check with your host.
Rizal says:
Comment posted on 08/5/10 @ 10:27 am
i am still having same the problem.. an error can not find the host? any ideas….
Diane Vigil says:
Comment posted on 08/5/10 @ 12:11 pm
Hard to tell. Have you tried any of the solutions posted above?
JG says:
Comment posted on 08/7/10 @ 9:54 am
I seem to be having an issue with connecting to FTP through Dream Weaver CS4 on Mac OSX version 10.5.7. I was uploading fine to my website through Dream Weaver. I then decided to redo the site to make it better and now for the life of me I can't connect anymore.
It doesn't even look like its trying to connect, the error appears instantly. I merely click test and it says can't connect. There is no wait time, changing the time out time did nothing.
I have tried the IP address and nothing. I have tried the ftp address and nothing. I have changed my password even to see if I was typing it wrong and still nothing.
I honestly don't think its even trying to connect. I have been at this for a few days now and I'm pretty close to losing my mind. I paid a lot of money to get a host and domain name through Godaddy.com and its just not working.
Any ideas as how I should approach this?
Diane Vigil says:
Comment posted on 08/7/10 @ 11:35 am
Hi, JG. I don't have a Mac, so I can't advise there — but I've helped clients with Macs connect via Dreamweaver, so I don't think that's the issue.
You didn't mention when you got the GoDaddy hosting, but their FTP setup is a little different. See the second part of my Comment #19:
The thing with GoDaddy is finding your actual server path, which isn't obvious when you FTP in. Let's say your username is xyz444. Your server path for Dreamweaver might be:
Root Directory: /
Web URL: http://yoursite.com/home/content/x/y/z/html/
-or-
http://yoursite.com/home/content/x/y/z/somenumbers/html/
I got that information from GoDaddy techs — but, to be honest, they don't all have that information.
See if that helps. If not, I would call GoDaddy.
AR says:
Comment posted on 08/10/10 @ 2:11 pm
Alright I got mine to work now after opening up a support ticket with my host.
Baisically change your http://ftp.yourwebsite.com to IP address like mentioned above, in your host directory just put /public_html/ and use passive FTP.
Now it works perfectly fine for me so if anyone is still having trouble try it out, might work out for you as well.
Diane Vigil says:
Comment posted on 08/10/10 @ 2:21 pm
Thanks! Although I don't think this would work in any case:
http://ftp.yourwebsite.com
It would have to be something like:
http://ftp.yourwebsite.com
or
yourwebsite.com
But … whatever works. :)
AR says:
Comment posted on 08/10/10 @ 4:36 pm
Oh ye apologies, it came out wrong.
I meant to say change your ftp host from http://ftp.yourwebsite.com to it's IP address
Diane Vigil says:
Comment posted on 08/10/10 @ 4:46 pm
Yes, I understood. Regardless of the IP address issue, I'm just saying that putting the http:// in front of http://ftp.yourwebsite.com will not work in any case.
EDITED: Oh, I see what's happening. When we write ftpDOTsomething, WordPress puts the http:// in front of it. (How annoying!)
Claudia says:
Comment posted on 09/23/10 @ 12:36 pm
In Dreamweaver 8, when I TEST my login and password via Site > Manage Sites > Edit > Remote Info I get the message: "Macromedia Dreamweaver connnected to your web server successfully".
But when I try to connect to the remote host via the connect butoon or by uploading a document, I get the message: "An FTP error occurred — cannot make connection to host…"
I tried all the fixes above but none worked.
I talked to our remote host folks, and they could see in the log when I connected successfully, and could see when I immediately tried to connect and failed and that they said this time it showed up as Anonymous on their side.
But they were not able to help me figure out WHY this happened…
Oh, and if I try to FTP the files up via Windows Explorer, there is no problem with the login and password there.
So, it sounds like DW issue???
Thanks for any and all help!!!!!
Diane Vigil says:
Comment posted on 09/23/10 @ 12:43 pm
Ah, the oddities …
When you connect to the remote host, can you click on the little square icon (Connect to Local and Remote Host) … can you see the server files?
I've never seen a situation in which DW verified that it could connect to the remote host but, on upload, was unable to connect.
I wonder why you were identified in the server logs as Anonymous. I'd look further into that.
Diane Vigil says:
Comment posted on 09/23/10 @ 12:45 pm
Hmm. I'm wondering whether you have the server path to the document root correctly in the Site specifications; for example:
public_html/
or
www/htdocs/
I don't know that your server would disconnect you if the site/document root was incorrect, but it might.
Claudia says:
Comment posted on 09/23/10 @ 12:51 pm
I hadn't changed anything. Is it possible that the folks who redesigned our website made some such change? I will ask them.
Thanks!!!
Claudia says:
Comment posted on 09/23/10 @ 12:56 pm
Oh, something you said just triggered something…(and to forewarn you…I am not super techno knowledgeable and may not succesfully explain myself well)….but our I.T. consultant recently created a script when our office computers shut down and restart which disconnects and reconnects our drives, including our server where our local DW/website documents are held. Do you think that could have anything to do with this?
Diane Vigil says:
Comment posted on 09/23/10 @ 1:05 pm
Okay. Did you check to see whether you're able to view the remote site (the server) in DW?
I would talk to your IT department in any case.
Claudia says:
Comment posted on 09/23/10 @ 2:13 pm
Yes, I can view the remote site in DW.
I was able to "get" or download a file from the remote site.
But I could not "put" or upload a file back up to the remote site without getting the "FTP…."error.
That makes no sense to me…
Thanks for your help so far Diane.
Diane Vigil says:
Comment posted on 09/23/10 @ 2:19 pm
Okay. I am wondering if your new designers had changed the file permissions on the site … such that you can't overwrite anything on the server.
claudia says:
Comment posted on 09/23/10 @ 3:44 pm
I'll ask, but they are not terribly responsive.
Thanks again for your ideas.
dudi says:
Comment posted on 10/22/10 @ 12:27 pm
hello,
I read through this tread. But i still can not connect to server in DW… :(
I`m using CS3 DW and my host is godaddy. I did try the tip above for godaddy. The result is that this time at least DW is tryed to connect (which instantly gave me hopes..lol) but then gives me a dialog box for "FTP error occurred". Did try SFTP and passive FTP as well, no change.
I am able to connect to server with filezilla, but I am unable to upload my flash (swf and html) files. Actually, it shows as uploaded file but does not show in browser.
Any further tip I could try?
Thanks
dudi says:
Comment posted on 10/22/10 @ 12:41 pm
I tried comment#19 but the part I am not really sure about is when you say
"Let's say your username is xyz444. Your server path for Dreamweaver might be:
Root Directory: /
Web URL: http://yoursite.com/home/content/x/y/z/html/
-or-
http://yoursite.com/home/content/x/y/z/somenumbers/html/"
Why only the "…x/y/z/…" is in the path and the "444″ is not from the hypothetical username?
Diane Vigil says:
Comment posted on 10/22/10 @ 12:58 pm
Hi dudi. You are probably going to have to call GoDaddy about this.
> Why only the "…x/y/z/…" is in the path and the "444? is not from the hypothetical username?
I have no idea; I just know that that was what worked … they only used the first three characters of the username, or the first three characters plus some numbers. It's all a GoDaddy mystery. :)
You might also try your GoDaddy documentation which I presume you received when you signed up with them.
dudi says:
Comment posted on 10/22/10 @ 3:00 pm
Thanks Diane for the explanation!
I tried with the first three characters and with their provied numbers, but still no connection.
I`ll call them again… at least now I know what specific question to ask.
Thank you
V says:
Comment posted on 11/11/10 @ 8:59 pm
I tried all suggestions on this post and Dreamweaver was not connecting untill I checked my "LittleSnitch" rules. Make sure that if you use "LittleSnitch" that your rules allow Dreamweaver to connect to your host.
I hope this helps
Diane Vigil says:
Comment posted on 11/11/10 @ 9:02 pm
I hate it when it's something like that. Glad you figured it out.
RB says:
Comment posted on 11/30/10 @ 2:00 pm
I'm trying to connect via FTP using Dreamweaver CS3 and did this process:
Site > Manage Sites > New (FTP and RDS server) > >
Name: DummyName
Access type: FTP
FTP host: http://www.dummyname.com (have tried http://www.dummyname.com:21, dummyname.com:21, dummyname.com)
Host directory: blank
Login: login
Password: password
URL prefix: http://www.dummyname.com/
I've tried checking "Use passive FTP" and "Use firewall" individually and together. My firewall settings are:
Always show: Local Files on the Right
Dependent files: checked (prompt on get/check out)
FTP connection: Disconnect after 30 Minutes idle
FTP time out: 60 seconds
FTP transfer options: Select default action in dialogs after 30 seconds
Firewall host: blank
Firewall port: 21
Move options: checked
I have also played around with Server Compatibility – unchecking "Use FTP performance optimization"
But it still gives me the "Operation Timed Out..Cancelling.." Any ideas? I did try this:
FTP host: http://ftp.irs.gov
Host directory: leave it blank
Username: anonymous
Password: leave it blank
to check if there's a firewall preventing me from connecting and that worked.
Diane Vigil says:
Comment posted on 11/30/10 @ 2:12 pm
Okay. I haven't seen DW CS3, but I have these comments:
- FTP host should be a domain name, or domain name and port (e.g., site.com:21) *if* the port is needed. No http, no www.
- URL Prefix: not sure what this is, but I would leave it blank and let DW pick up the information.
- Have you tried SFTP? Some servers won't let you FTP in insecurely. (Port is usually 22, but again, DW should pick that information up without you filing it in.)
Lastly, are you able to FTP to the server with any other FTP program?
RB says:
Comment posted on 11/30/10 @ 2:59 pm
Hi Diane. So I spent hours on this and the simple fix was just plugging in to the wall vs using WiFi at this office I'm in.
Diane Vigil says:
Comment posted on 11/30/10 @ 3:02 pm
Geez. :) Well, at least it's sorted out.
Darshi says:
Comment posted on 01/22/11 @ 7:37 pm
I Tried everything in this blog and still couldn't connect with DW (but could with filezilla so knew my setting were right)
Finally that comment about littlesnitch gave me the clue. I noticed that the website I used to find out my ip address was giving me the wrong numbers but littlesnitch was able to convert the url to ip correctly when I made a new rule. Ahhhhhh!!!!
Must be something to do with a shared ip, anyway I would suggest the most reliable way to get your correct ip is through Cpanel (or whatever your server uses) It should be listed on the left column.
Diane Vigil says:
Comment posted on 01/22/11 @ 9:54 pm
> I noticed that the website I used to find out my ip address was giving me the wrong numbers but littlesnitch was able to convert the url to ip correctly when I made a new rule.
Interesting. Glad you were able to find the solution (and the real IP address).
Mark says:
Comment posted on 03/6/11 @ 6:24 am
This has been a HUGE help!
Nothing here solved my issue – however gave me a TON of things to check, do, recheck, and test.
So, thank you!
My DW MX 2004 would not connect to my website hosted (free hosting) by GoDaddy. I spent a whole hour thumbing through the internet and reading forums and blogs of people with the same issue.
While I can not speak for DW CS3/4/5 etc, I was able to get my DW MX2004 to work.
It had NOTHING to do with DW.
I would recommend to EVERYONE having an issue getting DW to connect to their hosting server to check the following:
ROUTER – Check your router settings, in some rare cases, you may have to turn ON the FTP in Port Forwarding.
FIREWALL – If you are running a firewall on your Router, make sure you have allowed the proper connections. If you are running a firewall on your computer, or a program like snitch, make sure you have allowed the connection.
My issue was with my ESET firewall. It is very peculiar (I love it) and I had to make a rule for DW to allow it to connect to and be connected from my web server.
I can almost guarantee that 99% of the time, it will NOT be an issue with DW, or your Site Configuration.
However, that said, the following is a VALID example of a site configuration for DW MX2004 using GoDaddy (free) hosting:
Using the Advanced Tab;
Local Info:
The only thing here you need to make sure is correct is the "HTTP address:" box. You MUST type in the fully qualified http address, i.e.
http://www.YourDomain.ext/ (where .ext is the extension .com .net .whatever – http://www.Example.org – for instance)
Also in the Advanced tab;
Remote Info;
Access: FTP
FTP host: ftp.YourSite.ext
(no, you do not need http:// or ftp:// or ftp:)
(–this is assuming you have NOT change ANY values in your DNS records at your registrar – whereas the default for the CNAME ftp is usually @ (or host) – if you have no idea what I just typed, ignore it as you most probably didn't change anything in your zone file)
Host Directory: LEAVE THIS BLANK
Login: your ftp login ID
Password: your ftp login ID password
DO NOT CHECK:
Use passive FTP
Use firewall
Use Secure FTP (SFTP)
Now, here is where it gets tricky. Once you have all the proper info typed in above click TEST.
If you still have an issue, click the Server Compatibility… button. UNCHECK the box "Use FTP performance optimizaiton"
This should allow your DW MX2004 to connect to your GoDaddy web host – provided you have allowed DW to do so via any firewall both local to your PC or on your router.
Thank you!
Mark says:
Comment posted on 03/6/11 @ 6:27 am
Please NOTE in the above that this blog software automatically puts "http://" in front of the web address used in FTP Host: As noted however, you DO NOT need to use http://, ftp://, or ftp: in front of the address. You ONLY need "ftp.YourSite.ext"
Diane Vigil says:
Comment posted on 03/6/11 @ 7:51 am
Mark, thanks for your input. You're right that WordPress (the blog software) adds "http://" to the ftp line above. I was able to take the http:// out, in case anyone is wondering why it isn't there.
Thanks for your extensive information.
jeremy says:
Comment posted on 04/5/11 @ 1:49 pm
Thanks Mark, post 69
After hours of mucking about I tried the settings you suggested and it works. Lord only knows why, but it does.
Thanks you
Jeremy
Geoff says:
Comment posted on 06/6/11 @ 8:54 pm
I am a web developer with many site profiles, and had FTP issues sometime back with Dreamweaver CS3. . It turned out that one of the site definitions had become corrupt. So I backed them up and restored them and all was resolved.
Cheers,
Geoff
ionrane says:
Comment posted on 06/11/11 @ 9:09 pm
I'm baffled.
I've had dreamweaver settup properly for my remote server.
I added a local testing server, which seems to be settup right – all works well UNTIL I try to
"Put" files to the remote server.
For some reason, it seems, instead to connect to the local XAMPP server. Of course, that means it just looks to see about overwriting the file with itself.
If there is a whole directory of files to upload, then I DW's file transfer dialog (not nearly as informative ad Filezilla's transfer logs) runs for a long time. In the end, I see no changes.
What could possibly be causing it to connect to the testing server to upload files?
BTW, in manager, "Test" seems to connect to the remote server fine. (Took me a few tries to get that right initially), and if I change anything, including password, It no longer connects – this is the only clue I have that it's Testing the Remote connection, rather than simply connecting locally to the testing server !
? Any Suggestions ?
Diane Vigil says:
Comment posted on 06/11/11 @ 9:31 pm
I don't use the local testing server feature, but it sounds it's doing what's described in Tad confused with Dreamweaver's Local View, Remote View, and Testing Server — although there's no solution presented. I suspect that that's the way it's supposed to work.
But here's a solution from Murray, who's been a Team Macromedia Volunteer for Dreamweaver since before Adobe bought Macromedia: Managing sites: local, remote, testing.
ionrane says:
Comment posted on 06/14/11 @ 2:05 pm
Thanks for your reply.
The first link, basically re-states my problem, but as you stated, there is no solution.
The second link, well the solution to the problem posed is exactly what I'm already doing..
I must say I am impressed you found articles related to my problem!
I have still had a difficult time finding a useful set of search terms for this particular issue. And still haven't been able to find a solution.
Thank You so much for taking the time to research and respond to my question.
Your Site is a Beautiful Site, By The Way..
:)
————————————————————-
I don't think I clearly indicated the configuration I chose; I hope you don't mind the recap..
-In site manager, I have the remote server setup.
This has been established for quite some time. Nothing there has changed.
TESTing my "Remote Server" via the link on its BASIC tab STILL Connects to my Web Server Successfully.
-I installed a testing server (on my computer). My local site files are still in "thehrprofessionalsgroup" directory, but it has been moved to reside under the XAMPP (htdocs) directory, as required by xampp. This is akin to the directory on your remote server which runs your live website(s).
-In site manager, I updated the "Local Site Folder," to the new location.
-In site manager, I added an "xampp Testing Server" definition. Doing so in DW (CS5 and above) allows visual editing of dynamic wordpress files – Handy! Love It. Point is, this Clearly indicates my testing server is setup correctly. Yea!
Problem:
Now, when I "Put" a file (from my local/testing location), instead of connecting, like it should, to the remote server, it establishes a "remote" connection back to my Local server. ..And I think it actually copies the file into itself. Very Weird.
It seems to ignore the Site Manager -> Servers – "REMOTE" checkboxes. It acts as if my "Xampp Testing Server" has Both "Testing" and "Remote" boxes checked, while my "Remote Server" has Neither..
Diane Vigil says:
Comment posted on 06/14/11 @ 2:17 pm
I think I understand — when you're trying to put (upload) to the remote server, DW is uploading to your testing server.
Murray's solution ("Create two sites") is a good one, although it seems slightly complex — however, it does seem to acknowledge that there's a problem with the testing server/remote server scenario.
I'd just set up the site twice in DW (that is, make two Site definitions) … once for the testing server, and the second one for the real (remote server).
Typically, when I'm designing sites for clients, I upload to a domain on our server where they can check out the progress, we can discuss, etc. However, once it's done, I just switch the DW Site definition (of the server location) to their server/web hosting account and upload the whole thing there.
This would be somewhat the same … just two Site setups for one website; use the one for the testing server while you're working on it, and switch to the other when it's upload time.
Does that make sense, and do you think it would work?
(And thanks for the compliment on my website.)
ionrane says:
Comment posted on 06/14/11 @ 2:44 pm
Here is my workaround:
Disable the Testing Server definition to temporarily restore "Put" functionality.
In Site Manager: Servers tab -> select the testing server definition (I had labeled mine "XAMPP Testing Server"), and Uncheck "Testing" box ("Remote" should already be Unchecked).
So, I guess the workflow could be:
-Enable Testing Server to edit files in DW;
-Disable Testing Server to "Put" files on the Remote Server. (or use stand alone FTP software.)
————————————————————-
For me, 95% of the time, I prefer Filezilla to upload, download, and view my remote server directory. But, there are a few circumstances when I prefer having DW upload my files, so this "fix" hardly impacts my workflow.
If I used DW for all, or most, of my remote operations, I would find it to be quite a pain!
In that case, I would find it easier to create two site definitions in Site Manager:
-One with a Testing Server.
-The other, (almost) identical, but with Only a Remote server.
Then just switch between the two "sites" from the File panel before/after uploading.
If you do this, you'll have to ignore following warning:
"The root folder you have chosen is the same as the folder for site '…'. This may cause some operations, such as synchronization, to work incorrectly. Proceed anyway?'
Just click OK. I think that if it is the only method you use for uploading files (to that site), synchronization could still work, but I haven't tested that.
I have never had problems by having site definitions with overlapping/nested folders. However, as I also use FTP software, I hardly pay attention to synchronization states. I'm interested in finding out if anyone knows how the above settup would impact synchronization tracking.
ionrane says:
Comment posted on 06/14/11 @ 3:00 pm
( Sorry, I just noticed your solution when I hit send.. )
I did not anticipate my response would have been read so soon, and was busy coming up with the (same) solution and writing it up. I guess also I didn't read Murray closely enough to see any difference from what I was doing.
Your response is quite Clear. :)
WOW! .
Thanks again for your response :D !
ionrane says:
Comment posted on 06/14/11 @ 4:37 pm
Hey, I found a new Solution to this problem!
In Site Manager -> Servers – double click on your [Remote Server definition]
Choose "Advanced" tab.
Testing Server -> Server Model:
choose PHP MySQL .
(or whatever is appropriate for your site – it would be whatever you chose for your REAL testing server. Or perhaps it doesn't matter, as long as it is not "none" – after all, it looks to your Testing Server definition for testing and running locally in DW).
Save.
That's it!
Under Site Manager -> Servers
for your Remote server definition name: checkmark "Remote", uncheck "Testing"
for your Testing server definition name : uncheck "Remote", check "Testing"
With these settings, everything works as expected !
————————————————————————————————-
IMHO: If the Remote site is Not being used as a testing server, I don't think it is appropriate, or correct to choose any Testing Server Model (other than "none") for the Remote (Non-Testing) Server definition. I see it as a bug introduced when CS5.5 overhauled it's Site Manager dialog box, but kept part of it's code using the legacy model. At best it is simply confusing.
To me, it makes sense to set a Server Model for the Remote Server Only if it IS Also the Testing Server.
Yet in such a case, having the drop down "Testing" server box in this location is redundant to having the Testing server Checkbox on in the "Server" main dialog. Worse, in fact, it allows contradictory settings (the hence the conflict I was experiencing) when: 1)Testing server Unckecked, and Testing Model: indicates a server model other than "none", such as "php MySQL", for example), OR 2)Testing server is Checked, but the Testing Server Model set to: "None".
Instead, I think in Site Manager -> Server dialog..
under the "Testing" column..
next to each Testing Checkbox..
-move the Testing Server Model drop-down box to this location.
This would keep everything clearly defined!
No Conflicts. No Confusion. Nothing hidden.
Thanks for the voice..
;)
Diane Vigil says:
Comment posted on 06/14/11 @ 4:43 pm
Really nicely done, ionrane. Thanks!
(From your lips to Adobe's ears. Crossing my fingers.)
Diane Vigil says:
Comment posted on 10/28/11 @ 7:23 pm
For anyone trying to solve the testing server problem, note also Gordon's solution (Comment #1) in Dreamweaver FTP testing server and remote server problems.