You could try with an FTP app to confirm that the authentication/path info is correct. I think someone else recently had a similar issue and even though they checked with their hosting provider, the info was still wrong.
Btw, is that publishing setup for a draft version? The website address doesn’t look correct. You should not have “/index.html/” on the end of you domain.
I’d agree with Don that your web address looks odd. But also your path. It doesn’t typically have the web address included. And according to this article, Little Oak (which I don’t know if it’s up to date or not) advises to only put /www in the path
Can you access your own website directly from your browser using the machine that you use to publish? Or do you get a “Can’t find server” message when looking at your website directly on the internet?
The reason I ask is that Little Oak has an automated security process that will occasionally put my own development machine on an IP ‘blacklist’ and stop me connecting if I do anything that annoys their security settings and makes my activity appear ‘malicious’.
The thing is, the only thing that seems to set off their blacklist is using the Sitelok membership system admin page - or more specifically, if I leave a browser tab open with the Sitelok admin page running a plugin called “whoisonline”.
I don’t want to bog down here and derail the conversation, but my point is that it took me a long time to work out why Little Oak would periodically stop me accessing my website (via FTP or even just when trying to look at my own site over the internet). It came down to a webpage that was making to many Ajax calls and Little Oak didn’t like it.
So now if I suddenly find that I can’t access my site or connect via FTP, then I log in to my Little Oak Admin Manager - and usually there is a nasty warning sign waiting for me as soon as I log in that says “Your IP address has been blacklisted”. However, you can then click on a button to remove the block and get back to normal functioning. This very situation happened to me today…
The server name being just an IP address, would be hard to tell if it’s correct. It’s been years since I had a website at little oak, but looking through my old bookmarks and the server name was:
ftp.yourdomain.com
The path was: /www
Generally if you have the path cleared out and hit test, and still can’t connect, there’s usually something wrong with server name, username or password.
If it was me I would test those credentials with a FTP client like transmit. If you don’t have a stand-alone FTP client you can get FileZilla, it’s a free open source FTP app that works very well.
Really appreciate all the suggestions. None helped so a little at a loss as to where to go next. Guess I’ll cycle back to Little Oak but they were pretty clear that the entries were correct.
If it doesn’t work with an FTP, you can rule out RapidWeaver. It will also be much easier for you to deal with support at Little Oak if you can tell them you can’t connect with Filezilla.