On Thursday 29 January 2015 11:25:24 Vincent Lefevre wrote:
Ici, foobar.bar.net est le nom d'hôte canonique.
Le nom canonique (CNAME) CaNonical Name,
et le FQDN sont-ils les mêmes ?
Domaine = fruit.com Cname = www.fruit.com
Alias de www.fruit.com = p. ex. apple
Le nom canonique correspond à un
On 2015-01-29 13:01:11 +0100, andre_deb...@numericable.fr wrote:
On Thursday 29 January 2015 11:25:24 Vincent Lefevre wrote:
Ici, foobar.bar.net est le nom d'hôte canonique.
Le nom canonique (CNAME) CaNonical Name,
et le FQDN sont-ils les mêmes ?
La question n'a pas de sens: un CNAME est
Le 29/01/2015 11:25, Vincent Lefevre a écrit :
Perso, je pensais qu'une ligne du type :
adresse-IP
était complètement équivalent à :
adresse-IP
Pourquoi est-ce que ce n'est pas le cas ?
C'est équivalent pour la résolution directe, mais pas pour la
résolution
On 2015-01-29 23:51:57 +0100, Francois Lafont wrote:
Ok, effectivement, si sur une Debian Wheezy je mets
127.0.0.1 toto.domain.tld toto
alors la commande « hostname -f » me renvoie toto et
non toto.domain.tld ce qui prouve bien que l'ordre
L'inverse je suppose. hostname -f va normalement
On 2015-01-26 11:54:44 +0100, andre_deb...@numericable.fr wrote:
On Sunday 25 January 2015 22:52:11 Eddy F. wrote:
En gros, tu trouves qu'indiquer
127.0.0.1 n_importe_quoi.pas_utilisé_ailleurs localhost
n'est pas logique (et tu as raison !) mais l'ordinateur l'accepte et la
doc n'a
On 2015-01-28 16:02:39 +0100, andre_deb...@numericable.fr wrote:
Il faut savoir interpréter les man.
Il faut surtout avoir la bonne interprétation!
Je réitère dans /etc/hosts :
# 127.0.0.1 = adresse littéraire local de l'ordinateur :
127.0.0.1 localhost localhost.localdomain
# IP intranet
Bonsoir,
Le 28/01/2015 16:37, Vincent Lefevre a écrit :
# 127.0.0.1 = adresse littéraire local de l'ordinateur :
127.0.0.1 localhost localhost.localdomain
# IP intranet si réseau intranet, p. ex. 192.168.0.0
192.168.0.1 eddy eddy.eddy.net
Non! eddy.eddy.net doit être *avant* eddy.
Cf
Il faut savoir interpréter les man.
Je réitère dans /etc/hosts :
# 127.0.0.1 = adresse littéraire local de l'ordinateur :
127.0.0.1 localhost localhost.localdomain
# IP intranet si réseau intranet, p. ex. 192.168.0.0
192.168.0.1 eddy eddy.eddy.net
Si on écrit : 127.0.0.1 localhost eddy.net
Le mercredi 28 janvier 2015 à 16:02, andre_deb...@numericable.fr a écrit :
# 127.0.0.1 = adresse littéraire local de l'ordinateur :
127.0.0.1 localhost localhost.localdomain
# IP intranet si réseau intranet, p. ex. 192.168.0.0
192.168.0.1 eddy eddy.eddy.net
Si on écrit : 127.0.0.1
On Wednesday 28 January 2015 17:52:37 Francois Lafont wrote:
Le 28/01/2015 16:37, Vincent Lefevre a écrit :
# 127.0.0.1 = adresse littéraire local de l'ordinateur :
127.0.0.1 localhost localhost.localdomain
# IP intranet si réseau intranet, p. ex. 192.168.0.0
192.168.0.1 eddy
veux pas que
l'on croit que je préconise de mauvaises pratiques.
Le 26 jan 2015 à 11:54 (+0100)
andre_deb...@numericable.fr a écrit:
[...]
Tu dois évidemment différencier les deux hôtes et les deux domaines
dans /etc/hosts : 1] localhost localhost.localdomain = 127.0.0.1
2] eddy eddy.eddy.net
n_importe_quoi.pas_utilisé_ailleurs localhost
n'est pas logique (et tu as raison !) mais l'ordinateur l'accepte et la
doc n'a rien contre. Pourtant tu en déduis que c'est une faute, non pas
de bonne pratique, mais de... Ben je ne sais pas de quoi au fait.
Ce n'est pas parce que l'ordinateur l'accepte
Salut,
Zuthos Oddy a écrit le 25/01/2015 09:30 :
Mince, j'ai crié victoire trop vite.
Mon ping localhost fonctionne.
Par contre, lorsque j'écris localhost dans la barre du navigateur, il
m'envoie sur google. Par contre, 127.0.0.1 fonctionne.
Si quelqu'un avait une idée
C'est
On Saturday 24 January 2015 23:53:18 Eddy F. wrote:
Le 24 jan 2015 à 23:07 (+0100)
andre_deb...@numericable.fr a écrit:
Il faut bien lire le man jusqu'au bout et en bas :
127.0.0.1 localhost
192.168.1.10toto.mondomaine.orgtoto
192.168.1.13titi.mondomaine.orgtiti
compétence -- pour qu'une
de mes rares interventions vire au troll.)
Si un ordinateur n'a pas de carte réseau (ou assimilée), il ne peut
communiquer. /etc/hosts contiendra cette ligne :
IP =127.0.0.1 | nom et domaine littéraires : localhost
localhost.localdomain Linux fonctionne en mode terminal
Houps,
Je viens de voir que mon /etc/nsswitch.conf
indiqué hosts: dns
au lieu de hosts: files dns
Merci tous de même...
citation de=Zuthos Oddy
Bonjour,
Voici le résultat d'un ping sur localhost:
# ping -c 3 localhost
ping: unknown host localhost
Par contre:
# ping -c 3 127.0.0.1
On Saturday 24 January 2015 20:00:29 yamo' wrote:
# cat /etc/hosts
127.0.0.1 localhost.enfants localhost :
surtout pas !
127.0.0.1 est l'adresse IP locale par défaut.
Elle permet à l'ordinateur de dialoguer avec lui même,
car Linux fonctionne en mode terminal/serveur,
même en
Le 24 jan 2015 à 23:07 (+0100)
andre_deb...@numericable.fr a écrit:
Il faut bien lire le man jusqu'au bout et en bas :
127.0.0.1 localhost
192.168.1.10toto.mondomaine.orgtoto
192.168.1.13titi.mondomaine.orgtiti
Mais ce ne sont que des exemples. Rien ne dit que
citation de=andre_deb...@numericable.fr
On Saturday 24 January 2015 20:00:29 yamo' wrote:
# cat /etc/hosts
127.0.0.1 localhost.enfants localhost :
surtout pas !
127.0.0.1 est l'adresse IP locale par défaut.
Elle permet à l'ordinateur de dialoguer avec lui même,
car Linux
On Saturday 24 January 2015 22:57:30 Eddy F. wrote:
Le 24 jan 2015 à 20:48 (+0100) andre_deb...@numericable.fr a écrit:
On la déclare toujours comme ceci :
127.0.0.1 hostname hostname.domain domain
soit :
127.0.0.1 localhost localhost.localdomain localdomain
à l'exclusion de toutes
Salut,
Zuthos Oddy a écrit le 24/01/2015 16:50 :
Bonjour,
Voici le résultat d'un ping sur localhost:
# ping -c 3 localhost
ping: unknown host localhost
Par contre:
# ping -c 3 127.0.0.1
PING 127.0.0.1 (127.0.0.1) 56(84) bytes of data.
64 bytes from 127.0.0.1: icmp_req=1 ttl=64
Hello,
Le 24/01/2015 17:32, Zuthos Oddy a écrit :
Houps,
Je viens de voir que mon /etc/nsswitch.conf
indiqué hosts: dns
au lieu de hosts: files dns
Merci tous de même...
C'est une configuration que tu avais modifié toi même ou c'était par
défaut quand tu es arrivé dans le fichier ?
De
Bonjour,
Voici le résultat d'un ping sur localhost:
# ping -c 3 localhost
ping: unknown host localhost
Par contre:
# ping -c 3 127.0.0.1
PING 127.0.0.1 (127.0.0.1) 56(84) bytes of data.
64 bytes from 127.0.0.1: icmp_req=1 ttl=64 time=0.051 ms
64 bytes from 127.0.0.1: icmp_req=2 ttl=64 time
Hi.
On Tue, 26 Aug 2014 23:12:05 +0100
Karl E. Jorgensen k...@jorgensen.org.uk wrote:
4) sysctl --system
sysctl --system
* Applying /etc/sysctl.d/99-sysctl.conf ...
net.ipv4.icmp_echo_ignore_all = 0
net.ipv4.icmp_echo_ignore_broadcasts = 0
These caught my eye: Ignore all ICMP ?
Hi.
On Wed, 27 Aug 2014 00:27:24 +0100
Brian a...@cityscape.co.uk wrote:
On Wed 27 Aug 2014 at 02:01:14 +0400, Reco wrote:
And, by the way, ipv6 has nothing to do with this problem, although the
output of ipv6 routing tables looks abnormal to me too.
You could very well be correct.
On 26/08/14, Karl E. Jorgensen (k...@jorgensen.org.uk) wrote:
sysctl --system
* Applying /etc/sysctl.d/99-sysctl.conf ...
net.ipv4.icmp_echo_ignore_all = 0
net.ipv4.icmp_echo_ignore_broadcasts = 0
These caught my eye: Ignore all ICMP ? That would stop ping
(a.k.a. ICMP echo) from
.icmp_echo_ignore_broadcasts = 0
These caught my eye: Ignore all ICMP ? That would stop ping
(a.k.a. ICMP echo) from working, wouldn't it?
In this case 0 means 'false'. I.e.
net.ipv4.icmp_echo_ignore_broadcasts = 0
equals to
'do not ignore icmp echo broadcasts'.
Karl, Reco,
That did it. ping localhost
On 25/08/14, Reco (recovery...@gmail.com) wrote:
Date: Mon, 25 Aug 2014 22:13:41 +0400
From: Reco recovery...@gmail.com
To: debian-user@lists.debian.org
Subject: Re: No localhost - I'm stumped
X-Spam-Status: No, score=-11.2 required=4.0 tests=DKIM_SIGNED,DKIM_VALID,
DKIM_VALID_AU
On Tue 26 Aug 2014 at 15:50:25 -0400, John wrote:
On 25/08/14, Reco (recovery...@gmail.com) wrote:
3) strace ping6 -c2 ip6-localhost
I've left this one out, since I recompiled the kernel without ip6
support. ping6 localhost had produced a result and my thinking was
to force whatever
Hi.
On Tue, 26 Aug 2014 15:50:25 -0400
John johnrchamp...@wowway.com wrote:
-A POSTROUTING -j MASQUERADE
This is the source of your trouble. You're redirecting packets intended
to go via loopback to nat with this rule, which is obviously wrong.
I suggest you to try this rule instead:
Hi
On Tue, Aug 26, 2014 at 03:50:25PM -0400, John wrote:
On 25/08/14, Reco (recovery...@gmail.com) wrote:
Date: Mon, 25 Aug 2014 22:13:41 +0400
From: Reco recovery...@gmail.com
To: debian-user@lists.debian.org
Subject: Re: No localhost - I'm stumped
X-Spam-Status: No, score=-11.2
On Wed 27 Aug 2014 at 02:01:14 +0400, Reco wrote:
And, by the way, ipv6 has nothing to do with this problem, although the
output of ipv6 routing tables looks abnormal to me too.
You could very well be correct. But, should the OP decide to continue
without ipv6, he may find systemd to be
-but-localhost-whats-wrong
Thanks for the help and the link; it's useful. But alas, nothing from it s=
olved my problem. I think next I'll try reinstalling stuff -- cups, hplip,=
anything else that comes to mind -- and see if I blunder into a fix.
Still, it would be nice to _understand_
:
http://unix.stackexchange.com/questions/26487/can-ping-any-hosts-but-localhost-whats-wrong
Thanks for the help and the link; it's useful. But alas, nothing from it
s=
olved my problem. I think next I'll try reinstalling stuff -- cups,
hplip,=
anything else that comes to mind -- and see
into a fix.
Probably won't do you any good, since you have a basic kernel facility
(ip routing) in a broken state.
Still, it would be nice to _understand_ ...
Can you please post the output of (run it all as root):
1) iptables-save
2) strace ping -c2 localhost
3) strace ping6 -c2 ip6-localhost
For some days now, localhost has not responded to anything. I've tried
everything, and am stumped. Here are a few indications:
ifconfig shows lo is working:
loLink encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP
On 2014-08-24, John johnrchamp...@wowway.com wrote:
I've tried everything I can think of, and hints regarding what to try next
would be higholy welcome.
Some things to try here:
http://unix.stackexchange.com/questions/26487/can-ping-any-hosts-but-localhost-whats-wrong
--
To UNSUBSCRIBE
On Sun 24 Aug 2014 at 13:43:25 -0400, John wrote:
For some days now, localhost has not responded to anything. I've tried
everything, and am stumped. Here are a few indications:
netstat -an |grep 631
tcp0 0 127.0.0.1:631 0.0.0.0:* LISTEN
tcp0
Brian wrote:
Bob Proulx wrote:
Brian wrote:
or, if the domain name is left blank,
127.0.1.1 foo
would be seen.
Doesn't it create an entry like this? I will need to test it in order
to see what it creates in that case.
127.0.1.1 foo.localdomain foo
I will
On Fri 13 Jun 2014 at 15:28:48 -0600, Bob Proulx wrote:
Brian wrote:
Bob Proulx wrote:
Brian wrote:
True. What do think about the lack of '127.0.1.1 localhost' in
It is the 127.0.1.1 localhost to which I was disagreeing. That
would be unusual. It is still the loopback device so
On Thu 12 Jun 2014 at 16:23:37 -0600, Bob Proulx wrote:
Brian wrote:
Tom H wrote:
Brian wrote:
Teresa e Junior wrote:
$ cat /etc/hostname
localhost
...
True. What do think about the lack of '127.0.1.1 localhost' in
etc/hosts? Squeeze and Wheezy installs would both put
Brian wrote:
Bob Proulx wrote:
Brian wrote:
True. What do think about the lack of '127.0.1.1 localhost' in
It is the 127.0.1.1 localhost to which I was disagreeing. That
would be unusual. It is still the loopback device so off the top of
my head I think everything should still work okay
Brian wrote:
Tom H wrote:
Brian wrote:
Teresa e Junior wrote:
$ cat /etc/hostname
localhost
...
True. What do think about the lack of '127.0.1.1 localhost' in
etc/hosts? Squeeze and Wheezy installs would both put this line in.
Process check! I think you have mixed up the two
as follows (assuming your machine's name is
'mpdserver'):
/etc/hostname:
mpdserver
/etc/hosts:
127.0.0.1 localhost
127.0.1.1 mpdserver
(you can also use the lan IP here if it is fixed and enabling the IPv6
entries could also help)
mpd.conf:
bind_to_address localhost
After making all
On Mon, 9 Jun 2014 09:53:31 +0400, Reco wrote:
Your network configuration may be the cause of this. Can you please run
mpc like this, and show the result:
strace -e trace=network mpc
$ strace -e trace=network mpc
socket(PF_FILE, SOCK_STREAM|SOCK_CLOEXEC|SOCK_NONBLOCK, 0) = 3
connect(3,
On Mon, 09 Jun 2014 02:02:02 -0400
Teresa e Junior teresaejun...@gmail.com wrote:
On Mon, 9 Jun 2014 09:53:31 +0400, Reco wrote:
Your network configuration may be the cause of this. Can you please run
mpc like this, and show the result:
strace -e trace=network mpc
$ strace -e
On Mon, 9 Jun 2014 10:30:09 +0400, Reco wrote:
So, mpc tries standard mpd socket and fails. Adding said socket to
mpd.conf (via bind_address) should solve the issue.
Just adding a path to the socket doesn't really solve the issue (I run
MPD as my user, so there is no access to /var/run). I
On Mon, Jun 09, 2014 at 03:16:00AM -0400, Teresa e Junior wrote:
On Mon, 9 Jun 2014 10:30:09 +0400, Reco wrote:
So, mpc tries standard mpd socket and fails. Adding said socket to
mpd.conf (via bind_address) should solve the issue.
Just adding a path to the socket doesn't really solve the
On Mon, 9 Jun 2014 11:49:15 +0400, Reco wrote:
Ok. Thinking about it, I beleive I may miss something. What does show:
strace -f mpc
OK, the first log is from when it fails, and the second from when the
Wifi is connected. You'll see it reads from /etc/hosts more than just
127.0.0.1 localhost
On Mon 09 Jun 2014 at 01:23:43 -0400, Teresa e Junior wrote:
$ cat /etc/hostname
localhost
I wouldn't use this in /etc/hostname. Contacting this machine from
elsewhwere on the network could prove frustrating.
$ cat /etc/hosts
127.0.0.1 localhost
This line is the complete contents of /etc
On Lu, 09 iun 14, 01:23:43, Teresa e Junior wrote:
Hello to all!
I've had this problem with previous versions of MPD, and now I'm using
0.18.7, but the problem persists. This is an odd situation: MPD is
configured to run on 127.0.0.1, but if the Wifi is disconnected in
NetworkManager, it
. You'll see it reads from /etc/hosts more than
just 127.0.0.1 localhost, but the rest are just comments, and so I
tried removing them, but it didn't make any difference.
Weird. Just weird. Try it like this:
1) Start as root:
/usr/sbin/tcpdump -nn -i any udp port 53 or udp port 5353
2) Run mpc
On Mon, 9 Jun 2014 09:55:06 +0100, Brian wrote:
On Mon 09 Jun 2014 at 01:23:43 -0400, Teresa e Junior wrote:
$ cat /etc/hostname
localhost
I wouldn't use this in /etc/hostname. Contacting this machine from
elsewhwere on the network could prove frustrating.
I think that is or was a basic
On Mon, Jun 9, 2014 at 4:55 AM, Brian a...@cityscape.co.uk wrote:
On Mon 09 Jun 2014 at 01:23:43 -0400, Teresa e Junior wrote:
$ cat /etc/hostname
localhost
I wouldn't use this in /etc/hostname. Contacting this machine from
elsewhwere on the network could prove frustrating.
The hostname
On Mon 09 Jun 2014 at 07:58:41 -0400, Tom H wrote:
On Mon, Jun 9, 2014 at 4:55 AM, Brian a...@cityscape.co.uk wrote:
On Mon 09 Jun 2014 at 01:23:43 -0400, Teresa e Junior wrote:
$ cat /etc/hostname
localhost
I wouldn't use this in /etc/hostname. Contacting this machine from
On Mon, 9 Jun 2014 11:56:25 +0300, Andrei POPESCU wrote:
Could you please post the output of 'ip a' after you disconnect the
WiFi?
Just in case, I'm posting the output of both when the Wifi is off and on:
$ ip a
1: lo: LOOPBACK,UP,LOWER_UP mtu 65536 qdisc noqueue state UNKNOWN
On Mon, 9 Jun 2014 13:27:21 +0400, Reco wrote:
Weird. Just weird. Try it like this:
1) Start as root:
/usr/sbin/tcpdump -nn -i any udp port 53 or udp port 5353
2) Run mpc in another shell.
3) Please post the contents of your /etc/nsswitch.conf
Nothing really happens in the tcpdump window
On Mon, Jun 9, 2014 at 8:10 AM, Brian a...@cityscape.co.uk wrote:
On Mon 09 Jun 2014 at 07:58:41 -0400, Tom H wrote:
On Mon, Jun 9, 2014 at 4:55 AM, Brian a...@cityscape.co.uk wrote:
On Mon 09 Jun 2014 at 01:23:43 -0400, Teresa e Junior wrote:
$ cat /etc/hostname
localhost
I wouldn't use
On Mon, Jun 9, 2014 at 8:39 AM, Teresa e Junior teresaejun...@gmail.com wrote:
$ sudo /usr/sbin/tcpdump -nn -i any udp port 53 or udp port 5353
tcpdump: verbose output suppressed, use -v or -vv for full protocol decode
listening on any, link-type LINUX_SLL (Linux cooked), capture size 65535
On Mon, Jun 9, 2014 at 9:58 PM, Tom H tomh0...@gmail.com wrote:
On Mon, Jun 9, 2014 at 4:55 AM, Brian a...@cityscape.co.uk wrote:
On Mon 09 Jun 2014 at 01:23:43 -0400, Teresa e Junior wrote:
$ cat /etc/hostname
localhost
I wouldn't use this in /etc/hostname. Contacting this machine from
I believe it's got something to do with NetworkManager, because mpc
started working as soon as I run:
$ sudo service network-manager stop
And then I run this, and while trying to connect, or later if connecting
fails, mpc won't work again:
$ sudo service network-manager start
The version of
is
'mpdserver'):
/etc/hostname:
mpdserver
/etc/hosts:
127.0.0.1 localhost
127.0.1.1 mpdserver
(you can also use the lan IP here if it is fixed and enabling the IPv6
entries could also help)
mpd.conf:
bind_to_address localhost
If you make all these changes it's probably a good idea
:
$ mpc
error: Failed to resolve host name
$ ncmpcpp
error: Failed to resolve host name
$ MPD_HOST=127.0.0.1 mpc
error: Failed to resolve host name
$ cat /etc/hostname
localhost
$ cat /etc/hosts
127.0.0.1 localhost
$ egrep -v '^#|^$' .mpd/mpd.conf
music_directory ~/.mpd/database
Hi.
On Mon, 09 Jun 2014 01:23:43 -0400
Teresa e Junior teresaejun...@gmail.com wrote:
I have asked for help at http://forum.musicpd.org/, but they said
something is not right in my network, and I believe that could be
actually the case.
Your network configuration may be the cause of this.
, Rick McCombs AD5DU wrote:
I installed Debian Wheezy 7.4 on my Tower and my laptop.
I installed apt-cacher on the tower and it work when I use it from
localhost.
snipped
It is commented out but that is supposed to be the default.
The default is *not* to allow access from all hosts
I installed Debian Wheezy 7.4 on my Tower and my laptop.
I installed apt-cacher on the tower and it work when I use it from localhost.
I did not change the default config, which allows connections from any host.
I am behind a home gateway and I'm not going to forward the port from
the outside
On 19/03/14 18:18, Rick McCombs AD5DU wrote:
I installed Debian Wheezy 7.4 on my Tower and my laptop.
I installed apt-cacher on the tower and it work when I use it from localhost.
Do you mean apt-cacher or apt-cacher-ng??
I did not change the default config, which allows connections from any
use it from
localhost.
Do you mean apt-cacher or apt-cacher-ng??
apt-cacher.
I did not change the default config, which allows connections from any host.
Are you sure? (Perhaps the default config has changed since I last used
it instead of apt-cacher-ng)
Your belief is incorrect
Wheezy 7.4 on my Tower and my laptop.
I installed apt-cacher on the tower and it work when I use it from
localhost.
Do you mean apt-cacher or apt-cacher-ng??
apt-cacher.
I did not change the default config, which allows connections from any
host.
Are you sure? (Perhaps the default
Debian testing ama64 bit kullanıyorum. apache2, php5, mysql-server, phpmyadmin
paketlerini kurdum. Bu paketleri kurarken benden hiç şifre istenmedi.
localhost/phpmyadmin e girdiğimde kodlar çıkıyor. localhost/~kullaniciadi
girdiğimde normal. ?
--
To UNSUBSCRIBE, email to debian-user-turkish
istenmedi. localhost/phpmyadmin e girdiğimde kodlar çıkıyor.
localhost/~kullaniciadi girdiğimde normal. ?
--
To UNSUBSCRIBE, email to debian-user-turkish-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact
listmas...@lists.debian.org
Archive:
http://lists.debian.org
localhost/phpmyadmin yazdığımda tam olarak anlamadım ama php kodlarına benzer
kodlar çıkıyor.
18/12/13 Çar tarihinde Semetey Coşkun semeteycos...@gmail.com şöyle yazıyor:
Konu: Re: localhost PhpMyAdmin
Kime: Gökhan Öztürk reveler...@yahoo.com
Kopya
Tesekkürler. Ev klasörümün izinlerinde değiştirdim public_html ye bağlanabildim.
02/12/13 Pzt tarihinde Remzi AKYÜZ linuxli...@gmail.com şöyle yazıyor:
Konu: Re: Localhost Sunucu İzni
Kime: Gökhan Öztürk reveler...@yahoo.com,
debian-user-turkish
Herkese selam. Bu zamana kadar localhost ile ev dizini içerisindeki public_html
klasörüne sorunsuz bağlandım. Yaklaşık bir hafta girmemiştim ama bugun
bağlanmaya çalıstıgımda 403 forbidden you don't have permission to access / on
this server hatasını verdi. Anladığım kadarıyla sunucuya erişim
On 12/02/2013 09:22 PM, Gökhan Öztürk wrote:
Herkese selam. Bu zamana kadar localhost ile ev dizini içerisindeki public_html
klasörüne sorunsuz bağlandım. Yaklaşık bir hafta girmemiştim ama bugun
bağlanmaya çalıstıgımda 403 forbidden you don't have permission to access / on
this server
SetEnvIf Remote_Addr ::1
dontlog SetEnvIf User-Agent .*internal dummy connection.* dontlog
CustomLog /var/log/apache2/other_vhosts_access.log vhost_combined
env=!dontlog
La pregunta o duda es, ¿por qué realiza esto?
Son conexiones que han muerto y lo notifica a localhost?
Está
El día 15 de noviembre de 2013 19:07, Maykel Franco
maykeldeb...@gmail.com escribió:
Hola buenas, me he montado un servidor en casa en debian con apache +
php + mysql, un entorno para realizar yo pruebas.
El caso es que me he encontrado esto en el access.log:
Apache/2.2.22 (Ubuntu) (internal
vhost_combined env=!dontlog
La pregunta o duda es, ¿por qué realiza esto?
Son conexiones que han muerto y lo notifica a localhost?
Ya he agregado esas lineas y he recargado apache. Veré haber si no me
notifica más esa linea en el log.
Saludos.
--
To UNSUBSCRIBE, email to debian-user-spanish-requ
Bonjour a tous,
Je cherche à faire un système d'authentification simple utilisant IMAP.
Pour cela, j'utilise en PHP le code :
$mbox = imap_open({localhost:143}INBOX, user_id, password);
ça ne fonctionne pas, pour comprendre, je commence par nmap localhost
qui me renvoi l'erreur :
Starting
On Tue, 16 Jul 2013 11:40:05 +0200
julien jul...@nura.eu wrote:
$mbox = imap_open({localhost:143}INBOX, user_id, password);
Connaissois point PHP, mais c'est une Cde qu'on ne trouve pas
dans la partie IMAP de horde.
Starting Nmap 6.00 ( http://nmap.org ) at 2013-07-16 11:27 CEST
Le 2013-07-16 12:25, Bzzz a écrit :
On Tue, 16 Jul 2013 11:40:05 +0200
julien jul...@nura.eu wrote:
$mbox = imap_open({localhost:143}INBOX, user_id, password);
Connaissois point PHP, mais c'est une Cde qu'on ne trouve pas
dans la partie IMAP de horde.
Oui, par exemple roundcube utilise sa
On Tue, 16 Jul 2013 12:59:35 +0200
julien jul...@nura.eu wrote:
Connaissois pô nan plus VPS d'OVH, mais est-ce que le webmail se
connecte à localhost ou bien à l'adresse IP normale (ou au FQDN)
de la machine?
Dans la config de roundcube l'adresse est 127.0.0.1 et ça
fonctionne.
OK
Le 2013-07-16 13:12, Bzzz a écrit :
nmap localhost
nmap 127.0.0.1
nmap mon adresse ip publique
toutes ces commandes renvoies :
route_dst_netlink: can't find interface lo
Même nmap mon adresse ip publique?
et quid de 127.0.0.2?
??? Je ne comprend pas ta question.
J'ai bien une interface
Le 2013-07-16 13:12, Bzzz a écrit :
On Tue, 16 Jul 2013 12:59:35 +0200
julien jul...@nura.eu wrote:
nmap localhost
nmap 127.0.0.1
nmap mon adresse ip publique
toutes ces commandes renvoies :
route_dst_netlink: can't find interface lo
Même nmap mon adresse ip publique?
et quid de 127.0.0.2
On Tue, 16 Jul 2013 13:32:29 +0200
julien jul...@nura.eu wrote:
Merci pour tes réponses Bzzz !
Malheureusement, ce sont plus des supputations que des
réponses (mais je supputes de luxe;-)
--
islar Purain mes parents ont trouvé ma partition caché, je suis trop
mort de honte et en plus
Il faut utiliser le flag --unprivileged de nmap.
La machine est une machine virtuelle, il doit y avoir des limitations
au niveau de l'interface réseau car elle ne peut pas entrer en mode
promiscuous. C'est ce que tente de faire nmap avec : nmap localhost en
root.
Un nmap en tant
, así que el primer problema que tuve
fue con lograr una instalación manual de spip con un localhost. Lo
primero que hice fue recurrir a synaptic e instalar pero no funcionó.
(...)
¿Y qué error te daba?
Porque los paquetes disponibles en los repositorios oficiales no deberían
dar
El Thu, 03 Jan 2013 09:27:59 -0600, Anamhoo escribió:
Saludos lista, Camaleón:
On 29/12/12 16:25, Camaleón wrote:
(...)
Lo primero que hice fue recurrir a synaptic e instalar pero no
funcionó.
(...)
¿Y qué error te daba?
Porque los paquetes disponibles en los repositorios
Saludos lista
Estoy tratando de aprender a usar spip (http://www.spip.net) en mi
computadora personal pero como soy una neófita en todo esto me atoro en
cosas que tal vez son muy simples, así que el primer problema que tuve
fue con lograr una instalación manual de spip con un localhost.
Lo primero
instalación manual de spip con un localhost. Lo
primero que hice fue recurrir a synaptic e instalar pero no funcionó.
(...)
¿Y qué error te daba?
Porque los paquetes disponibles en los repositorios oficiales no deberían
dar muchos problemas salvo que tengan algún bug o que sean realmente
complejos de
Selamlar. apache2, php5, mysql-server paketlerini sorunsuz kurdum.
phpMyAdmin paketini kurarken benden istenilen şifreleri 123456 yaptım ancak
iceweasel tarayıcımdan localhost/phpmyadmin/ adresinden kullanıcı adımı
root ve parolamı
123456 yapıyorum aşağıdaki hatayı veriyor.
#1045 MySQL
sorunsuz kurdum.
phpMyAdmin paketini kurarken benden istenilen şifreleri 123456 yaptım
ancak iceweasel tarayıcımdan localhost/phpmyadmin/ adresinden kullanıcı
adımı root ve parolamı
123456 yapıyorum aşağıdaki hatayı veriyor.
#1045 MySQL sunucusuna oturum açılamıyor.
Root olarak kök etc
: Localhost phpMyAdmin
Merhabalar,
MySQL'e komut satırından bağlanabiliyor musunuz root kullanıcısı ile?
$mysql -u root -p
Komutundan sonra şifrenizi soracak. Buraya 123456 yazdığnızda giriş
yapabiliyor musunuz?
2012/11/17 Gökhan Öztürk reveler...@yahoo.com
Selamlar. apache2, php5, mysql-server
...@gmail.com
*Kime:* Gökhan Öztürk reveler...@yahoo.com
*Kopya:* debian-user-turkish@lists.debian.org
debian-user-turkish@lists.debian.org
*Gönderildiği Tarih:* 17 Kasım 2012 10:27 Cumartesi
*Konu:* Re: Localhost phpMyAdmin
Merhabalar,
MySQL'e komut satırından bağlanabiliyor musunuz root
Gönderildiği Tarih: 17 Kasım 2012 11:59 Cumartesi
Konu: Re: Yan: Localhost phpMyAdmin
Yani ;
mysql -u root
dediğinizde doğrudan bağlanabiliyorsunuz bu durumda anladığım kadarı ile.
Bildiğim kadarı ilen PHPMyAdmin'deki hiç bir aracın kendi şifresi yok...
Sorulan kullanıcı adı ve şifre veri
Aşağıdaki iki komutun çıktısını gönderebilir misiniz?
*
*
*
*
*$telnet localhost 3306*
*$lsof -i | grep mysql*
Bağlanamadınızda verilen hatayı da tam olarak geçebilir misiniz?
2012/11/17 Gökhan Öztürk reveler...@yahoo.com
Konsole ekranından şife yazmadan bağlanabildim ama web tarayıcısından
Coşkun semeteycos...@gmail.com
*Kime:* Gökhan Öztürk reveler...@yahoo.com
*Kopya:* debian-user-turkish@lists.debian.org
debian-user-turkish@lists.debian.org
*Gönderildiği Tarih:* 17 Kasım 2012 11:59 Cumartesi
*Konu:* Re: Yan: Localhost phpMyAdmin
Yani ;
*mysql -u root*
*
*
dediğinizde
mysql show grants;
+-+
| Grants for root@localhost |
+-+
| GRANT ALL PRIVILEGES ON *.* TO 'root'@'localhost' WITH GRANT
GRANT PROXY ON ''@'' TO 'root'@'localhost' WITH GRANT OPTION
Bu ne için gerekli? Proxy ile ulaşmaya mı çalışıyor acaba? Sorun buradan
kaynaklı olabilir. Proxy kullanıyor musunuz?
On Sat, Nov 17, 2012 at 12:47 PM, Gökhan Öztürk reveler...@yahoo.comwrote:
mysql show grants
: Localhost phpMyAdmin
GRANT PROXY ON ''@'' TO 'root'@'localhost' WITH GRANT OPTION
Bu ne için gerekli? Proxy ile ulaşmaya mı çalışıyor acaba? Sorun buradan
kaynaklı olabilir. Proxy kullanıyor musunuz?
On Sat, Nov 17, 2012 at 12:47 PM, Gökhan Öztürk reveler...@yahoo.com wrote:
mysql show grants
101 - 200 of 1065 matches
Mail list logo
