If EverWeb says Can't find directory path (Error 78), the Directory/Path in your publishing settings doesn't match a folder on your web host's server. Ask your host for the exact path for the protocol you use. Then enter it in File > Edit Publishing Settings and publish again.
What you may see
- In the error window, a Protocol Error such as creating the dir/file failed: No such file or directory.
- In the text you copy with Copy To Clipboard: Error: 78 Can't find directory path. Please check the directory path with your web hosting provider and enter the correct one in EverWeb's Publishing Settings.
Test Connection can still say "Your FTP details appear to be correct". The test checks that EverWeb can sign in. It doesn't check the folder.
Fix it
- Ask your host for the path. You can send them these words:
I publish my website with EverWeb using [FTP / FTP with SSL/TLS / FTP with SSH]. What is the exact Directory/Path for my website's main folder on that connection?
- Open your project and go to File > Edit Publishing Settings.
- In Directory/Path, enter exactly what your host gave you. Don't leave it empty, and don't enter your website address or the server name.
- Leave Subdirectory empty, unless you publish a second website or a test copy into its own folder.
- Click Test Connection.
- Go to File > Publish Entire Site, so every file goes to the right folder.
- Open your website in a private browser window to check your changes.
Tips about the path
- It's often
public_html, but each host is different. Some usehtdocsorwww, and some use a long path that only they can tell you. - The folder must already exist on the server. EverWeb creates the Subdirectory folder for you, but not the Directory/Path folder.
- The path can depend on the Protocol. If you change it, for example from FTP to FTP with SSH, ask your host for the path again.
- If your host gave a full path such as
/home/yourname/public_htmland you get Error 78, or publishing works but your changes don't appear, ask them whether it should be/public_htmlinstead. With FTP with SSH it's sometimes the other way round, and the full path is the one that works.
Let EverWeb check
In EverWeb 4.5 or later, go to Help > Publishing Connection Diagnostics and click Run Tests. It tests your connection and writes a report that suggests what to fix.
Still stuck?
Contact us with:
- the full error text (click Copy To Clipboard in the error window, then paste it)
- the diagnostics report (click Save Report)
- a full-screen screenshot of File > Edit Publishing Settings, with your password hidden
- what your host told you the path is