[Slackbuilds-users] slackbuilds site down =\

Jheengut Pritvi z.coldplayer at gmail.com
Sat Apr 8 06:12:58 UTC 2017


it is working now

On 7 April 2017 at 22:12, Matteo Bernardini <matteo.bernardini at gmail.com> wrote:
> 2017-04-07 19:54 GMT+02:00 Jheengut Pritvi <z.coldplayer at gmail.com>:
>> rsync is not working on my side though
>>
>> =======================
>> rsync slackbuilds.org::slackbuilds/14.2 .
>> rsync: failed to connect to slackbuilds.org (208.94.238.115):
>> Connection refused (111)
>> rsync error: error in socket IO (code 10) at clientserver.c(128)
>> [Receiver=3.1.0]
>> root@ # rsync rsync://slackbuilds.org/slackbuilds .
>> rsync: failed to connect to slackbuilds.org (208.94.238.115):
>> Connection refused (111)
>> rsync error: error in socket IO (code 10) at clientserver.c(128)
>> [Receiver=3.1.0]
>> root@ # nmap slackbuilds.org
>>
>> Starting Nmap 6.40 ( http://nmap.org ) at 2017-04-07 21:50 +04
>> Nmap scan report for slackbuilds.org (208.94.238.115)
>> Host is up (0.73s latency).
>> Not shown: 985 closed ports
>> PORT      STATE    SERVICE
>> 21/tcp    open     ftp
>> 22/tcp    open     ssh
>> 23/tcp    filtered telnet
>> 80/tcp    open     http
>> 113/tcp   open     ident
>> 135/tcp   filtered msrpc
>> 139/tcp   filtered netbios-ssn
>> 443/tcp   open     https
>> 445/tcp   filtered microsoft-ds
>> 1433/tcp  filtered ms-sql-s
>> 2967/tcp  filtered symantec-av
>> 9418/tcp  open     git
>> 13722/tcp filtered netbackup
>> 13782/tcp filtered netbackup
>> 13783/tcp filtered netbackup
>>
>> Nmap done: 1 IP address (1 host up) scanned in 20.30 seconds
>
> please, try again now.
> _______________________________________________
> SlackBuilds-users mailing list
> SlackBuilds-users at slackbuilds.org
> http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
> Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
> FAQ - https://slackbuilds.org/faq/
>


More information about the SlackBuilds-users mailing list