-
1. Re: Dreamweaver CS 5.5 not working with Godaddy FTP with TLS/SSL
mytaxsite.co.uk Aug 10, 2011 7:20 PM (in response to greenbluewave)Have you checked your configurations settings in DW? If so could you tell us how did you check them? I want to see if there is a flaw in your check process.
I know there is a problem with GoDaddy but what you are describing is not something I am aware of. If you reply with full details, I can tell you how to fix this problem once and for all.
hth
-
2. Re: Dreamweaver CS 5.5 not working with Godaddy FTP with TLS/SSL
greenbluewave Aug 10, 2011 9:56 PM (in response to mytaxsite.co.uk)Thank you for responding!
Have you checked your configurations settings in DW? If so could you tell us how did you check them? I want to see if there is a flaw in your check process.
It's works perfect with:
__________________________________________
Connect using: FTP
FTP Address: website.com Port: 21
Username: username
Password: password
Root Directory: / (or I can just leave that blank)
Web URL: http://website.com/
√ Use Passive FTP__________________________________________..It's when I change it to Connect using: FTP over SSL/TLS (implicit encryption) it fails to connect whether I use Authentication: Trusted server OR None (encryption only)..Or if it's FTP over SSL/TLS (explicit encryption) it fails to connect whether I use Authentication: Trusted server OR None (encryption only)..NOTE: With my Transmit FTP app, I connect to the exact same server flawlessly with FTP over SSL/TLS (explicit) on the same machine..I'm pretty sure this has something to do with the Godaddy certificate. Transmit is smart enough to allow me to "trust" the certificate on my Mac system keychain or whatever and will even work if I don't and click continue. I think that Dreamweaver's FTP just can't deal with the unsigned Godaddy certificate. I even tried trusting the certificate through Transmit's dialog. But, still Dreamweaver will not work even after trusting the certificate on my system. -
3. Re: Dreamweaver CS 5.5 not working with Godaddy FTP with TLS/SSL
mytaxsite.co.uk Aug 10, 2011 10:00 PM (in response to greenbluewave)How about setting up all over again using these instructions:
hth
-
4. Re: Dreamweaver CS 5.5 not working with Godaddy FTP with TLS/SSL
greenbluewave Aug 11, 2011 1:11 AM (in response to mytaxsite.co.uk)Already did that. Do you have a more specific suggestion?
-
5. Re: Dreamweaver CS 5.5 not working with Godaddy FTP with TLS/SSL
greenbluewave Sep 14, 2011 3:22 PM (in response to greenbluewave)I'm wondering has anyone ever been able to get Dreamweaver to work with Godaddy FTP with TLS/SSL or SFTP? Maybe I'm trying to do the impossible here. Such a shame that it works perfectly with Transmit. I have a feeling this has to do with Godaddy's certificate and Dreamweaver can't deal with it since it isn't trusted or whatever. Transmit is smart enough to let you ignore the warning, etc. and use it anyway, I wish the devs at Adobe would also put in that effort like the devs at Panic did.
:/
-
6. Re: Dreamweaver CS 5.5 not working with Godaddy FTP with TLS/SSL
SnakEyez02 Sep 14, 2011 3:41 PM (in response to greenbluewave)I looked over your post thus far and the following Godaddy FAQ article ( http://help.godaddy.com/article/4982 ). The setup is definitely FTPS explicit with no authentication if you are in a shared plan or trusted server if you are in a dedicated/VPS plan and you have your own certificate. Being that they neglect the port in their article, I would email them to ensure the port is correct.
Since you are on a Mac, please be sure that the button for denying the certificate was not accidentally declined. To verify this open up the Utilities in the applications folder, go to Keychain Access, and then on the left click for certificates. Your server's certificate should be in there and accepted. If you see the certificate and it is not trusted (red X), you can double click and change the trust settings for the certificate.
-
7. Re: Dreamweaver CS 5.5 not working with Godaddy FTP with TLS/SSL
greenbluewave Sep 14, 2011 4:11 PM (in response to SnakEyez02)Thank you so much for your helpful reply!
I had already trusted the certificate for godaddy a long time ago after Transmit mentioned it wasn't trusted so that Transmit would stop warning me. I double checked that and it's still trusted. I've been trying all kinds of configurations and everything either times out or I get this error:
With Transmit I'm connecting with FTP with TLS/SSL (explicit) with port 21 on Godaddy with no problem. I try that with Dreamweaver and I get that error above. I'm beginning to think Dreamweaver will simply never be compatible with Godaddy.
After all these years and the DW 5.5 update I had high hopes DW would finally work securely with Godaddy.
I really don't understand why Adobe devs don't focus on making sure Dreamweaver works securely with one of the most popular webhosts in the entire world?
Developers should be warned that it's not safe to use Dreamweaver with Godaddy at hotspots until the Adobe devs finally tackle this issue, if ever...
-
8. Re: Dreamweaver CS 5.5 not working with Godaddy FTP with TLS/SSL
SnakEyez02 Sep 14, 2011 5:29 PM (in response to greenbluewave)That doesn't make sense at all. You are obviously using the proper login to get that far. I tried searching a little more and everything seems to point to a specific error with an IIS server (FTP Error 534). Are you on a Windows server with Godaddy?
Also next time you try to log in can you go to Site->Advanced->FTP Log and then try to log in. Having the error from the log may give a little more insight.
-
9. Re: Dreamweaver CS 5.5 not working with Godaddy FTP with TLS/SSL
greenbluewave Sep 15, 2011 8:06 PM (in response to SnakEyez02)Are you on a Windows server with Godaddy?
Linux server
Also next time you try to log in can you go to Site->Advanced->FTP Log and then try to log in. Having the error from the log may give a little more insight.
Unfortunately, I've tried that before. Dreamweaver never gets that far, doesn't write anything to the FTP Log and just gives dialog box errors.
For example, here the DW dialog box error if I attempt
FTP over SSL/TLS (explicit encryption) - Authentication: Trusted server
DW dialog text: An FTP error occurred - cannot make connection to host. Server certificate is unsigned or not issued by a trusted certificate authority. In Site settings, set the authentication level to "None [encryption only)". Note that modifying this setting can adversely impact connection security.]
And here's the DW dialog box error if I attempt
FTP over SSL/TLS (explicit encryption) - Authentication: None (encryption only)
Background File Activity dialog text: 534 Fallback to [C]
DW dialog text: An FTP error occurred - cannot make connection to host. Protection level negotiation failed: Mismatch in encryption settings
-
10. Re: Dreamweaver CS 5.5 not working with Godaddy FTP with TLS/SSL
greenbluewave Sep 20, 2011 12:37 PM (in response to greenbluewave)Some Godaddy websites were hacked and Godaddy isn't sure how the credentials were aquired. I hope it wasn't via Dreamweaver at public hotspots.
-
11. Re: Dreamweaver CS 5.5 not working with Godaddy FTP with TLS/SSL
greenbluewave Sep 28, 2011 12:56 AM (in response to greenbluewave)Just figured I'd bump this in hopes someone who uses Godaddy with Dreamweaver can let me know if it's possible to have a secure connection with TLS/SSL?
-
12. Re: Dreamweaver CS 5.5 not working with Godaddy FTP with TLS/SSL
greenbluewave Oct 19, 2011 1:18 AM (in response to greenbluewave)I wonder, would anyone at Adobe like to correct or confirm this statement:
It's not safe to use Adobe Dreamweaver with Godaddy websites at hotspots, etc.
-
13. Re: Dreamweaver CS 5.5 not working with Godaddy FTP with TLS/SSL
MurraySummers Oct 19, 2011 5:18 AM (in response to greenbluewave)You won't get a reply from Adobe posting here. They only follow selected threads and even then it's irregular and unpredictable. If you need to contact them, you must do it directly.
See their website for contact information.
-
14. Re: Dreamweaver CS 5.5 not working with Godaddy FTP with TLS/SSL
SnakEyez02 Oct 19, 2011 5:29 AM (in response to greenbluewave)Some Godaddy websites were hacked and Godaddy isn't sure how the credentials were aquired. I hope it wasn't via Dreamweaver at public hotspots.
First, that's a Godaddy problem if their security isn't up to par.
Just figured I'd bump this in hopes someone who uses Godaddy with Dreamweaver can let me know if it's possible to have a secure connection with TLS/SSL?
Here's an offer I'm willing to make to you. Set me up with a FTP account on your hosting account. Point it to a dummy folder (permissions 755) with only a single "index.html" document inside. This way I only have access to the dummy folder. PM me the login details username/password, as well as the other Godaddy details, as you are using them (ftp address, security settings). Basically the only difference is that my account will go to a different folder within your hosting account upon login. I'll see what I can come up testing it out for a day or so.
BTW, I do also have Transmit on my Mac, so if it's going to happen I should be able to duplicate your exact situation on my Mac. If I can duplicate it, I'll stand right in line with you filing a bug report to Adobe re-enforcing that the bug is reproducible.
-
15. Re: Dreamweaver CS 5.5 not working with Godaddy FTP with TLS/SSL
greenbluewave Oct 20, 2011 4:44 PM (in response to SnakEyez02)SnakEyez02 wrote:
First, that's a Godaddy problem if their security isn't up to par.
That may be the case that Godaddy is also at fault, but every other FTP app I use with Godaddy works fine. It's just Dreamweaver and has always been just Dreamweaver not working with a secure connection to Godaddy. Considering Godaddy is the largest webhost in the USA, you'd think Adobe would have fixed this years ago. I should also mention I'm not endorsing Godaddy and I understand there's plenty of people that don't like Godaddy for very good reasons.
Sent you PM with FTP account with Godaddy yesterday. Thank you for taking a look!
UPDATE: Whoops, I see you responded via private message already. I'll paste most of it here in hopes it helps others to understand the issue:
via SnakEyez02 PM:
Ok this took a lot of digging. I won't say it's not a DW issue 100% and I will report a bug for your problem, but DW is not the problem alone Godaddy needs to share the blame here for a bad certificate. Here is what is happening:
I'll start with DW:
- The settings are correct that were in the post. Port 21, FTP explicit, and the authentication should be set to None (encyprtion only). This is where the transmission is encrypted using SSL, but the certificate is shared and not specific to the domain owner. That is the difference between DW's "none" and "trusted". It's a poor choice of words I'll give them that. However, Godaddy seems to want all connections to be trusted thus the other error you get when you turn on the None option. Now could DW do what Transmit does, warn you and write in an unsigned certificate into the Keychain app, probably, is it best practice for security reasons to "Trust" an unsigned certificate probably not.
Now Transmit:
- As explained above Transmit opens up a prompt to override and create a fake-trusted signed certificate. Thus by forcing the OS to think a legitimate certificate is there it gets you through albeit through unconventional methods.
The problem:
- A good portion of this problem lies with Godaddy. Now I use a shared hosting account and set one up on an independant host for a friend of mine and both of them accept the shared certificates (SSL explicit). The difference is the hostname of the certificate. I ran a traceroute (from Network Utility in Utilities folder) on your website and came up with the following address: 173.201.23x.x.
The problem is that the certificate on your server is actually not for that server which is the reason DW seems to have such an issue with it. The SSL certificate that Godaddy put on your shared server is for host - 173.201.19x.5x. As you can see, it's a certificate for another server. Honestly the fact that Panic's Transmit allows this override scares me a little bit and the fact that Godaddy never noticed this issue either scares me to. So while DW could write in a bad certificate I can see why this is happening.
I know there is not much solice in my answer because it still doesn't alleviate the problem that you have with DW connecting. Unfortunately I do not have a workaround despite my numerous attempts to try and gain access over a secure connection. One alternative you could ask Godaddy for in the meantime is an SSH connection which would allow you to use SFTP instead of FTPS. But that's a short-term solution to a long-term problem.
If you think of anything else feel free to bounce any ideas off me I don't mind. Good luck in getting this solved and I will post a bug report to make Adobe aware of the issue.
Thank you for looking into this issue in depth like you have!
I think the issue might be that Godaddy is applying cost saving measures to keep their prices down in the way they implement their certificates (but it also wouldn't surprise me to know it's simply ineptitude on Godaddy's part either). I'm not sure I fault Panic with Transmit much at all because it clearly warns you about the certificate and it's your choice to continue. And, as it stands now, it's much safer to continue to connect that way with Transmit than to stop and connect with no encryption at all at a public hotspot.
As it stands now, you really shouldn't connect to Godaddy with Dreamweaver at a public hotspot unless you set up an SSH tunnel with your connection first. But enabling SSH is an added expense in many ways including paying for the service, using more computer resources for tunneling and time setting it up and implementation... all because Dreamweaver won't just allow developers the option like Transmit does.
Once again, thank you for looking at this and I hope someone at Adobe finally address this issue for the security of its customers who use Godaddy (which is often not their choice and was, instead, the choice of their clients to use Godaddy as a webhost).
Just a side note, I contacted Godaddy support about this several years ago and they were unresponsive and even hostile about it - So that's definitely another vote against Godaddy from me as well.
Message was edited by: greenbluewave
-
16. Re: Dreamweaver CS 5.5 not working with Godaddy FTP with TLS/SSL
MurraySummers Oct 21, 2011 6:26 AM (in response to greenbluewave)Godaddy is the largest webhost? I hope not. I can't stand them....
-
17. Re: Dreamweaver CS 5.5 not working with Godaddy FTP with TLS/SSL
greenbluewave Oct 23, 2011 9:06 PM (in response to MurraySummers)Murray *ACP* wrote:
Godaddy is the largest webhost? I hope not. I can't stand them....
Yes, I don't don't blame you but alas, they are the largest webhost in the world. And when dealing with clients you will inevitably be working with Godaddy servers on occasion as a developer - that's why I'm so surprised to see Adobe ignoring this issue. Godaddy is relatively cheap and has a reliable uptimes at least.
-
18. Re: Dreamweaver CS 5.5 not working with Godaddy FTP with TLS/SSL
IntenseTech Oct 30, 2011 9:45 AM (in response to greenbluewave)Hi,
I came across this thread while also having a problem with FTP permissions when accessing a godaddy web server.
And so while this is not a exactly a direct answer to your TLS/SSL issue, I do think that it's imporant to note that there is another odd issue
with godaddy servers and the FTP client built within Dreamweaver, specifically 5.5.
Please reference the adobe blog post here: http://blogs.adobe.com/dreamweaver/2011/07/late-breaking-issue-putget-not-working-for-some -dreamweaver-cs5-5-users.html
but to summarize, there's some odd things going on the godaddy FTP if the original files are still there (these files are automatically put there when you set up hosting). Specifically,
- Delete or move the webformmailer.php file out of the root of the directory
- if problems continue, I'd remove any/all web hoster created files, and only put up files that are specially related to the site you're building.
- It's possible, (and this is really wierd), that only dreamweaver may see these files as existing. Filezilla or SmartFTP may not see these files, and thus may be unable to delete.
Oddness, eh!
Good luck,
-Logan
-
19. Re: Dreamweaver CS 5.5 not working with Godaddy FTP with TLS/SSL
Curtis_E_Flush Oct 30, 2011 12:19 PM (in response to greenbluewave)greenbluewave wrote:
Yes, I don't don't blame you but alas, they are the largest webhost in the world. And when dealing with clients you will inevitably be working with Godaddy servers on occasion as a developer - that's why I'm so surprised to see Adobe ignoring this issue.
MaDonald's sells more hamburgers than anyone on earth too, but that doesn't mean they make the best burgers. These days, people can "vote with their wallets" when confronted with bad service from a huge company that doesn't give a damn, be it GoDaddy or Adobe. I have only used three hosting services in 8 years, One I will never deal with again (primarily because they are now out of business) One I use for four sites I maintain for clients, and then there's Network Solutions, who are as bad as GoDaddy IMHO.
I'm taking over a GoDaddy site (actually two) next month and moving it to ICDSoft because there is about 70 lines of proprietary GoDaddy C-R-A-P in every page of the main site. The whole thing is a blooming mess, and I spent three days cleaning it all to show the client the difference.
Consistently, I hear bad things about GoDaddy FTP and DW, NetSol and DW. I have personally experienced bad things with NetSol and DW. Do I blame DW or Adobe? No because the FTP works in (it seems) every other environment except these two, so the problem is most likely in... you guessed it... these two hositng services and their configuration.
I donlt care if they ARE the biggest in the world, it just makes the fact that GoDaddy sucks all the more apparent.
IE used to tbe the most used browser in the world too. People finally got wise to their ways and now Firefox is more used by a slim margin. Bigger isn't always better. I think it's time for a new host.
-
20. Re: Dreamweaver CS 5.5 not working with Godaddy FTP with TLS/SSL
greenbluewave Nov 3, 2011 2:51 PM (in response to Curtis_E_Flush)MaDonald's sells more hamburgers than anyone on earth too, but that doesn't mean they make the best burgers.
I don't think you comprehended me. I've never claimed Godaddy is "the best" or even close to that. Go back and read through this thread if you still don't understand.
I think it's time for a new host.
In the real business world (as I've already explained previously) you don't always have that choice as a professional. And, in reality, I haven't even had issues with Godaddy except this one issue with Adobe Dreamweaver that doesn't manifest itself with any other FTP app I utilize including Transmit, YummyFTP, etc.
If Adobe would fix this issue with Dreamweaver, then that would be great. Because, once again, as I already stated, in the real world, if you are a developer with many clients, then you will inevitably be working with Godaddy servers on occasion. Telling a client they must change their webhost because the tool you use won't connect securely to thier website just isn't an option in most cases in the real business world.
Once again, Adobe should tackle this issue and fix it for those of us who pay for and utlitize their products in the real world. With your line of thinking, I guess developers shouldn't make websites for their clients that work with the inferior Windows operating system on principle, but that would be foolhardy at best.
I don't recommend Godaddy to clients, but in the real business world it's not always practical to tell a client to move their entire website to a new host from one they already happily use just because you as a developer choose to use an Adobe product.
I wish you luck in your endeavors.
-
21. Re: Dreamweaver CS 5.5 not working with Godaddy FTP with TLS/SSL
AllDayDev Nov 7, 2011 6:21 PM (in response to greenbluewave)If you want the Dreamweaver development team to add a feature that would allow you to accept an invalid certificate, then please let them know directly: http://adobe.ly/DWwish
A better recommendation might be to contact GoDaddy to see if you can get a certificate that matches the domain. This page should have the info you need to do this: http://bit.ly/vwoT6g
-
22. Re: Dreamweaver CS 5.5 not working with Godaddy FTP with TLS/SSL
Curtis_E_Flush Nov 12, 2011 4:58 PM (in response to greenbluewave)greenbluewave wrote:
Telling a client they must change their webhost because the tool you use won't connect securely to thier website just isn't an option in most cases in the real business world.
Once again, Adobe should tackle this issue and fix it for those of us who pay for and utlitize their products in the real world. With your line of thinking, I guess developers shouldn't make websites for their clients that work with the inferior Windows operating system on principle, but that would be foolhardy at best.
I don't recommend Godaddy to clients, but in the real business world it's not always practical to tell a client to move their entire website to a new host from one they already happily use just because you as a developer choose to use an Adobe product.
I wish you luck in your endeavors.
As a web designer and a reseller for a good stable hosting company, I can usually offer a far better deal to clients and prospective clients than GoDaddy, or Network Solutions or any of about a dozen other hosting companies can offer, because I get a deeper discount with each account I refer. And it applies to all my referred clients so everyone wins when they refer someone to me and I refer them in turn to my preferred hosting service. Can GoDaddy offer 20Gb of site space, unlimited 1Gb email boxes and 100Gb of traffic a month for $2.80? With eighteen clients presently, that's what they each pay, and there's 24/7 support with actual live people on the other end. GoDaddy doesn't offer that at the same price.
Everyone is free to choose their own host, but I like what I get for my clients for what they pay.
-
23. Re: Dreamweaver CS 5.5 not working with Godaddy FTP with TLS/SSL
greenbluewave Nov 15, 2011 12:29 AM (in response to Curtis_E_Flush)I don't think you are following my point. I'm not, repeat I am NOT, saying Godaddy is the best web hosting company. I'm NOT here to compare web hosts, nor compare pricing with you. I have your price beat with other web hosts, but it doesn't matter. I do NOT endorse, nor tell my clients to use Godaddy. I've already made this quite clear.
I'm here to discuss the issue that Dreamweaver doesn't work properly and securely with Godaddy, which whether you like it or not, is the world's largest web hoster. I've already clearly stated why as a professional who deals with many clients that I sometimes have no choice but to sometimes work with Godaddy servers. I really am not intersted in explaining that to you any further, either.
If you have some professional insight in how to make Dreamweaver securely work with Godaddy as the title of this thread implies, that'd be great. Otherwise, please avoid derailing and thread-jacking since it's not helpful to me whatsoever. If you'd like to start your own thread on the merits of various web hosting strategies, please have at it; it's not needed here.
Thank you.
As a web designer and a reseller for a good stable hosting company, I can usually offer a far better deal to clients and prospective clients than GoDaddy, or Network Solutions or any of about a dozen other hosting companies can offer, because I get a deeper discount with each account I refer. And it applies to all my referred clients so everyone wins when they refer someone to me and I refer them in turn to my preferred hosting service. Can GoDaddy offer 20Gb of site space, unlimited 1Gb email boxes and 100Gb of traffic a month for $2.80? With eighteen clients presently, that's what they each pay, and there's 24/7 support with actual live people on the other end. GoDaddy doesn't offer that at the same price.
Everyone is free to choose their own host, but I like what I get for my clients for what they pay.
-
24. Re: Dreamweaver CS 5.5 not working with Godaddy FTP with TLS/SSL
greenbluewave Nov 15, 2011 12:34 AM (in response to AllDayDev)If you want the Dreamweaver development team to add a feature that would allow you to accept an invalid certificate, then please let them know directly
Will do. But, I'm surprised the development team hasn't already addressed this issue themselves in testing like smaller companies like Panic Transmit have. But, if it's up to me, then I guess I'll do it. Thanks.
-
25. Re: Dreamweaver CS 5.5 not working with Godaddy FTP with TLS/SSL
SnakEyez02 Nov 15, 2011 6:07 AM (in response to greenbluewave)greenbluewave wrote:
If you want the Dreamweaver development team to add a feature that would allow you to accept an invalid certificate, then please let them know directly
Will do. But, I'm surprised the development team hasn't already addressed this issue themselves in testing like smaller companies like Panic Transmit have. But, if it's up to me, then I guess I'll do it. Thanks.
Green, I think the reason why this is sometimes overlooked is because of the following. Have you ever used a browser (the example I am using is Chrome) and received this page:
If you received a big red warning from DW like that as it should well give you for going to a site with invalid security, would you even bother to go through? It's a shame that companies feel they can provide this false sense of security to their end-users. In all honesty your connection might as well be over plain FTP. Even Microsoft says the same thing in a KB article about invalid security certificates ( http://support.microsoft.com/kb/813618 ) that something like you see is an improperly configured certificate, thus it is invalid.
Back to your point about:
I'm here to discuss the issue that Dreamweaver doesn't work properly and securely with Godaddy,
Dreamweaver is working properly, but it cannot work securely because of the invalid certificate. Even a web browser would do the same thing. I am sorry that Godaddy is causing this much trouble and that there is no way to tell Dreamweaver, go ahead insecurely I understand the risk, but as Carey mentioned, suggesting that as a feature and contacting your host are the only options you have.
-
26. Re: Dreamweaver CS 5.5 not working with Godaddy FTP with TLS/SSL
greenbluewave Nov 17, 2011 1:07 AM (in response to SnakEyez02)SnakEyez02 wrote:
If you received a big red warning from DW like that as it should well give you for going to a site with invalid security, would you even bother to go through? It's a shame that companies feel they can provide this false sense of security to their end-users. In all honesty your connection might as well be over plain FTP. Even Microsoft says the same thing in a KB article about invalid security certificates ( http://support.microsoft.com/kb/813618 ) that something like you see is an improperly configured certificate, thus it is invalid.
I respectfully disagree that using Godaddy's invalid certificate is worse than plain FTP at a hotspot. It's far better because at a hotspot you are far more likely to run into someone sniffing your completely unencrypted traffic. There's nothing worse than going to a hotspot and signing into FTP without any encryption at all. With products like Firesheep floating around out there, I'd say it's not wise at all.
And in that Microsoft support document, they do show where (just like all other FTP software I use) you can continue after the warning. I'm not saying Godaddy isn't at fault and is simply using this as a way to add hidden costs to their service which may very well be true (they charge and extra $70.00 per year for your own SSL certificate instead of the shared one) and I know of plenty of other webhosts that don't do that.
But the reality is, whether anyone likes it or not, they are the world's largest web hoster and it behooves Adobe not to make an industry standard WYSIWYG application work as securely as possible like other FTP apps do with the world's largest web hoster. While the Godaddy certificate issue is not great, it's certainly better than no encryption at all at a public hotspot.
They should just show a warning and then like Microsoft, Apple, Mozilla, Google, Panic Transmit, YummyFTP, etc. all do, allow you to continue after explaining the risks. For me to tell clients to pay more money for a quick job just so I can connect more securely at hotspots isn't always practical and VPNs aren't always practical either because of speed and incompatibility issues at some more stubborn hotspots.
Once again, I just wish Adobe would update their FTP to function like everyone else's does and give the warning and then allow you to continue. I don't think that's asking too much considering all the other apps out there that do it and it would be an upgrade in security to match all other products I've used as far as hotspots are concerned. Which is the only reason I'm concerned about this really is public hotspots and cheap Godaddy accounts. I sincerely wonder if there's already been some developers who've had websites hacked because they signed into Godaddy sites at hotspots without any form of encryption.
This is how it should be done when you connect. This is what Transmit does, it lets you view the certificate and everything. Certificates are much more important to protect from phising when surfing websites than in this circumstance. And, once again, the end result is encryption which is much better than nothing.
OPTIONS:
AFTER CLICKING SHOW CERTIFICATE (if you choose you can "always trust it" afterwards so you don't keep getting warnings)
Thank you and I really value your input. If you see where I'm wrong about this, please let me know.
-
27. Re: Dreamweaver CS 5.5 not working with Godaddy FTP with TLS/SSL
SnakEyez02 Nov 17, 2011 5:12 AM (in response to greenbluewave)I'm not saying your wrong, in fact I would say you are the victim here. However I do disagree about your statement that Godaddy is the largest, their statement is the largest domain registrar and the funny part "The world's largest hosting provider of secure websites" (real secure with invalid certificates, right?). I believe the title for largest hosting company in the world goes to SoftLayer right now, but that's beside the point.
I'm curious though, have you tried to contact Godaddy with this information about invalid certificates. I think we would all be interested to hear their response.
-
28. Re: Dreamweaver CS 5.5 not working with Godaddy FTP with TLS/SSL
greenbluewave Nov 18, 2011 6:14 AM (in response to SnakEyez02)SnakEyez02 wrote: I'm curious though, have you tried to contact Godaddy with this information about invalid certificates. I think we would all be interested to hear their response.
A long time ago and they said to purchase a certificate and that they wouldn't troubleshoot 3rd party software or something along that line.
On the plus side, I’m in contact with Adobe and they are using that FTP account I created to test the issue now. I also showed them how Transmit handles it, etc. - So, we'll see...........
UPDATE
Emailed with Adobe and after some testing, they've determinded it is indeed a bug in Dreamweaver and have now added it to their database. So hopefully in the future this will be fixed by an update.
Thanks to all for the input and help, especialy SnakEyez02.
Message was edited by: greenbluewave
-
29. Re: Dreamweaver CS 5.5 not working with Godaddy FTP with TLS/SSL
ProgOne Jan 26, 2014 8:30 PM (in response to greenbluewave)This is what I did to fix our issue.
- Connect using: FTP over SSL/TLS (explicit encryption)
- port 21
- Authentication: None (encryption only) You will see a site certificate once you press the 'Test' key. Its your choice to trust the certificate or not. I clicked continue (trust) and connected.
Also I clicked 'Passive', I haven't tested it with out it checked.
Enlarge the above picture by clicking on it.
Message was edited by: ProgOne
-
30. Re: Dreamweaver CS 5.5 not working with Godaddy FTP with TLS/SSL
jk45 Feb 6, 2014 12:44 PM (in response to greenbluewave)Well, i have big problems with godaddy too.
I manage 5 websites, and everything was running ok. I had just to upload the files from Dreamweaver, and everything was working fine.
I am no a pro in server, but it seems to me that go gaddy changed everything, so you have to do it manually.
The new controlpanel from godaddy is very difficult to manage... and why should I learn all that??? I just want to upload mi files...
I think for my next website I try another hosting...












