Koozali.org: home of the SME Server

FTP client accesses i-bay, but browsers - not

Offline leonp

  • **
  • 43
  • +0/-0
FTP client accesses i-bay, but browsers - not
« on: May 07, 2018, 01:42:50 PM »
Hello, all.
I have the i-bay which is configured as (w-group,r-everyone) and access for entire internet (password required).
When I run the FTP command client in Linux from outside it works fine.
But when I use the same address (in the form user:password@site.com) in any browser, I can't achieve the correct i-bay - it lands in the Primary i-bay.

How can I provide the users read access to the specific i-bay?

Thanks a lot ahead

Offline Jean-Philippe Pialasse

  • *
  • 2,762
  • +11/-0
  • aka Unnilennium
    • http://smeserver.pialasse.com
Re: FTP client accesses i-bay, but browsers - not
« Reply #1 on: May 07, 2018, 04:08:51 PM »
can you be more verbose and describe exactly what you do and using which software, so we can reproduce. Describe what you do , as it was a recipe, what you expect, and what you get.

Offline leonp

  • **
  • 43
  • +0/-0
Re: FTP client accesses i-bay, but browsers - not
« Reply #2 on: May 07, 2018, 05:47:56 PM »
I shall try... :-)
I run the Linux FTP client as
ftp mysite.com
220 192.168.50.254 FTP server ready
Name (srv:leonp): ibayX-name
331 Password required for ibayX-name
Password: password-for-ibayX-name
And here I see the i-bayX content and everything is fine.

Now, I go to Chrome browser, for example (with M$ Explorer the behavior is the same).
In the URL line I type:
ftp://ibayX-name:password-for-ibayX-name@mysite.com
and I expect here to see the content of the ibayX.
But instead I receive the content of the Primary i-bay, which will be displayed if no username:password is given.
This uname:passwd@site tehcnology worked fine with my old Fedora server, but doesn't work with SME server.

Thanks for your help.

Offline Jean-Philippe Pialasse

  • *
  • 2,762
  • +11/-0
  • aka Unnilennium
    • http://smeserver.pialasse.com
Re: FTP client accesses i-bay, but browsers - not
« Reply #3 on: May 07, 2018, 06:18:54 PM »
I assume mysite.com is pointing to an ibay, not to Primary.
What is the version of your SME ?
What is the version of your old fedora server , and more importantly its ftp daemon software and version ?

Have you checked the proftpd logs, you might find information or differences between the two client logins.
tail -f /var/log/ftp/current

Also  have you any tweak or custom template on this SME ?

I made a test with Firefox and Chrome, and I can only say works for me as intended with a SME9 ...

Offline leonp

  • **
  • 43
  • +0/-0
Re: FTP client accesses i-bay, but browsers - not
« Reply #4 on: May 08, 2018, 11:21:41 AM »
I assume mysite.com is pointing to an ibay, not to Primary.
As far as I understand, pointing to i-bay is done by giving user name equal to i-bay. At least it is what the help says:
" ftp://ibayname@ftp.domainname
  ftp://ibayname:password@ftp.domainname"
So, after re-reading this I tried the first line (the second lands in Primary) - it worked! It gave me name/password dialog in Chrome.
The way suggested in help: "www.yourdomain.xxx/i-bayname" doesn't connect to the server at all.

What is the version of your SME ?
It is 9.2

What is the version of your old fedora server , and more importantly its ftp daemon software and version ?
It was Fedora 6 which was about 10 years old...:-)

Have you checked the proftpd logs, you might find information or differences between the two client logins.
tail -f /var/log/ftp/current
I see the difference, but don't know how to explain it:

The Chrome failed connection in the form ftp://i-bay-name:passwd@site.com
@400000005af169e63b569aec tcpsvd: info: status 1/40
@400000005af169e63b58f094 tcpsvd: info: pid 27200 from 192.168.50.57
@400000005af169e700f907f4 tcpsvd: info: concurrency 27200 192.168.50.57 1/4
@400000005af169e700f913ac tcpsvd: info: start 27200 0:192.168.50.254 ::192.168.50.57:53252 ./peers/192.168.50
@400000005af169e8277b6df4 tcpsvd: info: end 27200 exit 0
@400000005af169e8277b79ac tcpsvd: info: status 0/40

The Linux FTP client success conection:
@400000005af16a5918b38e14 tcpsvd: info: status 1/40
@400000005af16a5918b5e3bc tcpsvd: info: pid 27232 from 192.168.50.57
@400000005af16a5918b7c81c tcpsvd: info: concurrency 27232 192.168.50.57 1/4
@400000005af16a5918b7cfec tcpsvd: info: start 27232 0:192.168.50.254 ::192.168.50.57:53268 ./peers/192.168.50

Also  have you any tweak or custom template on this SME ?
No, only legacy installation.

I made a test with Firefox and Chrome, and I can only say works for me as intended with a SME9 ...
I foresaw it... :-)
That's why I supposed that something is wrong on my side...
But what?
Actually, it is not so critical now, when I know the workaround ( ftp://ibay@site.com).

Thank you very much for your help and time!

Offline Jean-Philippe Pialasse

  • *
  • 2,762
  • +11/-0
  • aka Unnilennium
    • http://smeserver.pialasse.com
Re: FTP client accesses i-bay, but browsers - not
« Reply #5 on: May 08, 2018, 03:11:43 PM »
As far as I understand, pointing to i-bay is done by giving user name equal to i-bay.
no this is done by configuring the domain in the domain panel of the server manager to point to the ibay. If you never set the domain on the server but have external dns pointing to the server, then it will behave as the primary domain and point to Primary.

if the domain is set on the ibay, http://domain.tld will show the html ibay content. If it is the primary domain or not configured it will show the primary content , and http://domain.tld/myibay will show your myibay content.

At least it is what the help says:
" ftp://ibayname@ftp.domainname
this could be considered as trying to connect without password and may fail with some non interactive clients.


  ftp://ibayname:password@ftp.domainname"
So, after re-reading this I tried the first line (the second lands in Primary) - it worked! It gave me name/password dialog in Chrome.
I used the second one on both fiefox and chrome without issue.

The way suggested in help: "www.yourdomain.xxx/i-bayname" doesn't connect to the server at all.
well if the domain point to the ibay of course it will fail.

the only difference in the log you paste is one did not yet disconnect.
well, good news you find a way !