Author Topic: ftp setting won't remember my password when entered  (Read 3114 times)

pete

  • Calm
  • *
  • Posts: 3
ftp setting won't remember my password when entered
« on: January 05, 2014, 05:24:29 AM »
ive spent most of the day searching for possible ways to fix this but i admit defeat and asking for help :)

trying to set up the ftp setting in WC and it tests ok, but once i click OK the password disappears thus rendering the upload feature broken.
and resulting in ftp error 902 password is blank.

does anyone here know how to solve this.?

and one other question. in the last screen shot. "couldn't write temporary custom web files"
thats another one that has me stumped.

thanks guys.

WC v 1.24 build 11
OS X 10.9.1


WCDev

  • WeatherCat Developer
  • Administrator
  • Storm
  • *****
  • Posts: 2987
    • CW9739
    • IIBSTO2
    • Trixology
  • Station Details: Main Station: Vantage Pro-2, 24hr fars, solar, extra temp stations, no U.V. WeatherLinkLive.
Re: ftp setting won't remember my password when entered
« Reply #1 on: January 05, 2014, 08:30:02 AM »
Pete,
The password is stored in your keychain - it sounds like there's some issue with it or the security of your user in general (the way it works is the keychain trusts WeatherCat because it is signed with an Apple certificate so you don't have to authorise WeatherCat to access it).

Check the state of your keychain with the Keychain utility (Applications->Utilities->Keychain) and that WeatherCat has access.

The second issue might suggest either you are out of disc space or a permissions issue (WeatherCat has no permission to write to disk) - again possibly an issue with the user you are logged in as.

First thing to do, is quit WeatherCat then delete your existing WeatherCat folder (maybe it was downloaded/installed as another user), download it again and run it (as the user you are logged in as).
 
If that's still the same, you can create a new user, log in as that user, download WeatherCat and run it as that user  - that'll tell you immediately if it's some problem with the user account you are using at the moment.