Hello TIm,

Is it possible for you to provide us with the back end and FTP access to your site to check on this issue?

Added credentials.
Same credentials as I used for my other open ticket.
Let me know if you have any problems connecting.

Hello Tim,

With the provided login, I can't see those stream items. Can you please provide us with the login credentials that would be able to see those stream items.

Mark, I logged in with the credentials provided, and was able to see the appropriate stream items by doing the following:
go to the site URL listed below
log in with the stackideas login (below)
click the "social" menu item
in the left column, under "news feed" select "everyone"
the posts from the screenshots are under "1 week ago"

I have reset the password, so please use what is listed in this reply.
Thanks!

Ah, thanks! I see the problem now but I can't seem to login to the FTP This is the error that I am getting, http://screencast.com/t/JEhHcLQFchLs . Can you please advise?

Adding new FTP Credentials.
Sorry for the mistake.

Let me know if you have any problems getting in.
Folder is /public_html/

Hello Tim,

Sorry for the delay of this reply, I tried to login with the provided login credentials for the FTP and I seem to hit the same error here, http://screencast.com/t/d0jSamw05

It seems our firewall was only open for SFTP Port 22 and not FTP Port 21.
I've opened FTP Port 21 as well so you should now be able to connect using standard FTP but if you have problems try using protocol SFTP on Port 22.
I've removed all connection limitations from the warsaw login.

I tested using the following site:
https://www.wormly.com/test_ftp_server

[Edit by moderator: Removed image attachment to protect user as it contains user's FTP password in clear text]

Thanks Tim, it works now but the site access now does not work

I can still login with your account.
Are you possibly messing up the username?


If your not able to access the site at all, please let me know.

Hello Tim,

Thanks! Found the problem and fixed on the site This will be fixed in the next release of the discuss app.