Log for Seamonkey Composer publishing?

After some Seamonkey crashing issues a few weeks back I had to reinstall Se=
amonkey and restore my profile from a backup of the profile directory. Ever=
ything has been working great since then except publishing web pages to a w=
eb server I manage. I've always been able to use Composer to edit pages and=
 then publish via the built-in site publish feature. There is nothing uniqu=
e about the destination. Just a simple FTP server.

In the past, the following info worked fine:

Publishing addres: ftp://ftp.<mysite>.com/public_html
Plain FTP connection
enter username/password in prompt

Now when I try to publish I immediately get a 'Publishing Failed' message i=
n the dialog. Is there a log file somewhere that may contain more informati=
on? Or a way to increase log level to a debugging level?

Thanks!
0
BigBlue
11/15/2019 5:14:07 PM
mozilla.support.seamonkey 13296 articles. 0 followers. Post Follow

5 Replies
19 Views

Similar Articles

[PageSpeed] 39

By the way, I have removed and recreated the publishing site profile several times and I know the information is correct. I can use FireFTP or command line FTP just fine.
0
BigBlue
11/15/2019 5:15:06 PM
BigBlue wrote:
> After some Seamonkey crashing issues a few weeks back I had to reinstall Seamonkey and restore my profile from a backup of the profile directory. Everything has been working great since then except publishing web pages to a web server I manage. I've always been able to use Composer to edit pages and then publish via the built-in site publish feature. There is nothing unique about the destination. Just a simple FTP server.
> 
> In the past, the following info worked fine:
> 
> Publishing addres: ftp://ftp.<mysite>.com/public_html
> Plain FTP connection
> enter username/password in prompt
> 
> Now when I try to publish I immediately get a 'Publishing Failed' message in the dialog. Is there a log file somewhere that may contain more information? Or a way to increase log level to a debugging level?
> 
> Thanks!
> 

Did you install the same level as you had previously?
We are talking Windows here?  (which version? Not that it makes much of 
a difference)

-- 
spammus ergo sum, viruses courtesy of https://www.nsa.gov/malware/
0
Don
11/15/2019 8:11:39 PM
On Friday, November 15, 2019 at 2:11:44 PM UTC-6, Don Spam's Reckless Son wrote:
> Did you install the same level as you had previously?
> We are talking Windows here?  (which version? Not that it makes much of 
> a difference)

Yes, I was at the latest Seamonkey version before the re-install. Windows 10 64-bit OS.
0
BigBlue
11/15/2019 9:18:15 PM
BigBlue wrote:
> On Friday, November 15, 2019 at 2:11:44 PM UTC-6, Don Spam's Reckless Son wrote:
>> Did you install the same level as you had previously?
>> We are talking Windows here?  (which version? Not that it makes much of
>> a difference)
> 
> Yes, I was at the latest Seamonkey version before the re-install. Windows 10 64-bit OS.
> 
I was hoping someone who has access to an ftp server could jump in here, 
I don't.  Do you have appropriate logging set up on the target machine? 
Something like firewall logs or logging of ftp failed access attempts? 
A sniffer is probably overkill.

-- 
spammus ergo sum, viruses courtesy of https://www.nsa.gov/malware/
0
Don
11/18/2019 2:14:34 PM
On Monday, November 18, 2019 at 8:14:41 AM UTC-6, Don Spam's Reckless Son w=
rote:
> I was hoping someone who has access to an ftp server could jump in here,=
=20
> I don't.  Do you have appropriate logging set up on the target machine?=
=20
> Something like firewall logs or logging of ftp failed access attempts?=20
> A sniffer is probably overkill.
>=20

It's a service provider so I don't think I have access to any logs on the s=
erver side. I was hoping for logs on my desktop for Seamonkey, since that s=
hould be more descriptive of the issue. And, since the 'publishing failed' =
message happens almost instantaneously after clicking 'publish' I'm not sur=
e a connection was even attempted, so there may not be anything on the serv=
er.

It's so weird since this is such a simple situation. There are only 4 basic=
 elements involved: server hostname, username, password, and, optionally, t=
he directory on the destination. And this exact setup worked flawlessly for=
 years before I had to re-install and move my profile backup back into plac=
e.
0
BigBlue
11/18/2019 3:15:33 PM
Reply: