Re: chromium http://localhost:80

On 1/22/24 10:23, Max Nikulin wrote: On 22/01/2024 02:50, gene heskett wrote: browser: chromium It was also true here using the file:// prefix, trying look at the html versions of the man pages in /usr/share/local/docs. /usr/share may be unavailable inside snap or flatpack sandboxes, so it

chromium http://localhost:80

On 22/01/2024 02:50, gene heskett wrote: browser: chromium It was also true here using the file:// prefix, trying look at the html versions of the man pages in /usr/share/local/docs. /usr/share may be unavailable inside snap or flatpack sandboxes, so it is expected. Even /etc/hosts,

Re: systemctl status mariadb - Access denied for user root at localhost using password NO

Hello, On Mon, Oct 02, 2023 at 04:45:25PM +0300, Petros Pap wrote: > root@server:~# mysql -u root > ERROR 1045 (28000): Access denied for user 'root'@'localhost' (using > password: NO) I believe that the Debian packaging of MariaDB is by default set up to allow socket authentication

systemctl status mariadb - Access denied for user root at localhost using password NO

from Webmin and create databases from phpmyadmin and i can login to mysql root@server:~# mysql -u root ERROR 1045 (28000): Access denied for user 'root'@'localhost' (using password: NO) root@server:~# mysql -u root -p Enter password: Welcome to the MariaDB monitor. Commands end with ; or \g. Your

Re: [Solved] Re: localhost web apps and cookie blocking

Proto $scheme; > proxy_set_header Connection ""; > allow 192.168.0.0/24; > allow 127.0.0.1; > deny all; > } > > This changes it from a port number to a URL path, allows your > local network and localhost to access it, and denies it to &

Re: [Solved] Re: localhost web apps and cookie blocking

hanges it from a port number to a URL path, allows your local network and localhost to access it, and denies it to others, should they come across the path. Apache and other webservers can do similar things. -dsr-

[Solved] Re: localhost web apps and cookie blocking

On Fri, 16 Apr 2021 17:26:36 +0300 Reco wrote: > Hi. > > On Fri, Apr 16, 2021 at 09:45:13AM -0400, Celejar wrote: > > I have various web (HTTP, not HTTPS) apps (e.g., pi-hole, Home > > Assistant) running on localhost (either actually on localhost, or on > > an

Re: localhost web apps and cookie blocking

Hi. On Fri, Apr 16, 2021 at 09:45:13AM -0400, Celejar wrote: > I have various web (HTTP, not HTTPS) apps (e.g., pi-hole, Home > Assistant) running on localhost (either actually on localhost, or on > another host but accessed via 'localhost' via ssh port forwarding > (

localhost web apps and cookie blocking

Hi, I have various web (HTTP, not HTTPS) apps (e.g., pi-hole, Home Assistant) running on localhost (either actually on localhost, or on another host but accessed via 'localhost' via ssh port forwarding (LocalForward) that require cookies to function (even before logging in). When Firefox is set

Re: localhost

On Sun, 2 Feb 2020 19:40:24 + "Russell L. Harris" wrote: > I am attempting to configure Apache2 (in Debian 10) as a local server > for web site development. > > I see on the "Apache2 Debian Default Page" the Debian logo; the > browser reports the image loc

Re: localhost

al server > for web site development. > > I see on the "Apache2 Debian Default Page" the Debian logo; the > browser reports the image location as: > > http://localhost/icons/openlogo-75.png > > But when I use midnight commander to snoop around \var and other > dir

localhost

I am attempting to configure Apache2 (in Debian 10) as a local server for web site development. I see on the "Apache2 Debian Default Page" the Debian logo; the browser reports the image location as: http://localhost/icons/openlogo-75.png But when I use midnight commander to sn

Re: password refused by cups on localhost:631 (fwd)

On Tue 03 Dec 2019 at 16:13:19 -0500, Gene Heskett wrote: > On Tuesday 03 December 2019 14:23:34 Brian wrote: > > > On Tue 03 Dec 2019 at 13:17:21 -0500, Gene Heskett wrote: > > > On Tuesday 03 December 2019 11:37:59 Pierre Frenkiel wrote: > > > > On Sat, 30 Nov 2019, Roberto C. Sanchez wrote: >

solved - Re: password refused by cups on localhost:631

On Tue, 3 Dec 2019, Brian wrote: I wish I could have confidence in your interpretation of what you see. The pop-up has two blank fields. Why you maintain the default user is "root" and it needs to be changed is beyond me. Yes, I maintain it... I don't have 2 blank fields, but 2 fields

Re: password refused by cups on localhost:631 (fwd)

On Tuesday 03 December 2019 15:58:45 Pierre Frenkiel wrote: > On Tue, 3 Dec 2019, Gene Heskett wrote: > > When it pops up the requester, did you change it from the default > > root to your name you've added to lpadmin and your passwd? That > > works here. > >yes, I do that, and my password

Re: password refused by cups on localhost:631 (fwd)

On Tuesday 03 December 2019 14:23:34 Brian wrote: > On Tue 03 Dec 2019 at 13:17:21 -0500, Gene Heskett wrote: > > On Tuesday 03 December 2019 11:37:59 Pierre Frenkiel wrote: > > > On Sat, 30 Nov 2019, Roberto C. Sanchez wrote: > > > It has a been a while, but my recollection is that you add a

Re: password refused by cups on localhost:631 (fwd)

On Tue, 3 Dec 2019, Gene Heskett wrote: When it pops up the requester, did you change it from the default root to your name you've added to lpadmin and your passwd? That works here. yes, I do that, and my password is refused, as well as the root one

Re: password refused by cups on localhost:631 (fwd)

On Tue 03 Dec 2019 at 13:17:21 -0500, Gene Heskett wrote: > On Tuesday 03 December 2019 11:37:59 Pierre Frenkiel wrote: > > > On Sat, 30 Nov 2019, Roberto C. Sanchez wrote: > > It has a been a while, but my recollection is that you add a > > normal user to the lpadmin group. Then by

Re: password refused by cups on localhost:631 (fwd)

On Tuesday 03 December 2019 11:37:59 Pierre Frenkiel wrote: > On Sat, 30 Nov 2019, Roberto C. Sanchez wrote: > It has a been a while, but my recollection is that you add a > normal user to the lpadmin group. Then by authenticating as that user > you can administer through the web interface.

Re: password refused by cups on localhost:631 (fwd)

On Tue 03 Dec 2019 at 17:37:59 +0100, Pierre Frenkiel wrote: > On Sat, 30 Nov 2019, Roberto C. Sanchez wrote: >It has a been a while, but my recollection is that you add a normal user >to the lpadmin group. Then by authenticating as that user you can >administer through the web

Re: password refused by cups on localhost:631 (fwd)

On Sat, 30 Nov 2019, Roberto C. Sanchez wrote: It has a been a while, but my recollection is that you add a normal user to the lpadmin group. Then by authenticating as that user you can administer through the web interface. hi Roberto, alas, I already did that, without success.

Re: password refused by cups on localhost:631

On Sat, 30 Nov 2019, Roberto C. Sanchez wrote: It has a been a while, but my recollection is that you add a normal user to the lpadmin group. Then by authenticating as that user you can administer through the web interface. hi Roberto, alas, I already did that, without success.

Re: password refused by cups on localhost:631

On Sat, Nov 30, 2019 at 06:01:18PM +0100, Pierre Frenkiel wrote: > hi, > I tried to add a printer using the localhost:631 cups interface, > but the root password was refused, as well as mine > To be sure that the provided password was valid, I reset it with the > passwd command

password refused by cups on localhost:631

hi, I tried to add a printer using the localhost:631 cups interface, but the root password was refused, as well as mine To be sure that the provided password was valid, I reset it with the passwd command. can anybody explain that? best regards, -- Pierre Frenkiel

[Résolu] Re: Le paramètre "scratchDir" que vous avez spécifié: [/opt/alfresco/work/Catalina/localhost/ROOT] est inutilisable.

leurs, je viens de vérifier) : > > " Le paramètre "scratchDir" que vous avez spécifié: > [/opt/alfresco/work/Catalina/localhost/ROOT] est inutilisable." > > D'après mon ami google, il s'agirait d'un problème de droit. Mais non, > pas ici, puisque le

Le paramètre "scratchDir" que vous avez spécifié: [/opt/alfresco/work/Catalina/localhost/ROOT] est inutilisable.

mètre "scratchDir" que vous avez spécifié: [/opt/alfresco/work/Catalina/localhost/ROOT] est inutilisable." D'après mon ami google, il s'agirait d'un problème de droit. Mais non, pas ici, puisque le répertoire en question appartient bien à l'utilisateur tomcat:tomcat (le mêm

smbclient not finding share for localhost

My home linux/Debian/buster machine has suddenly made samba 'shares' invisible to my Win7 virtual machine (running under kvm/qemu). Using smbclient I get two different responses: smbclient -L localhost only gives the error-message response: Unable to initialize messaging context

Re: cannot open display: localhost:0.0

D=1000=gene > > What is this telling me? That your X server isn't listening to TCP. Which is normal in this century. That's why we have DISPLAY=:0 instead of DISPLAY=localhost:0. (Or, your X server isn't running at all. But since you seemed to expect to see something, I'm guessing that you act

Re: cannot open display: localhost:0.0 [solved]

without -nolisten tcp flag. Unfortunately: $ xhost +localhost; DISPLAY=localhost:0.0 xterm localhost being added to access control list xterm: Xt error: Can't open display: localhost:0.0 Any suggestions?? Did you check port 6000? root@pc6:~# netstat -anp | grep 6000 tcp   0   0 0.0.0.0:6000

Re: cannot open display: localhost:0.0 [solved]

: $ xhost +localhost; DISPLAY=localhost:0.0 xterm localhost being added to access control list xterm: Xt error: Can't open display: localhost:0.0 Any suggestions?? Did you check port 6000? root@pc6:~# netstat -anp | grep 6000 tcp   0   0 0.0.0.0:6000   0.0.0.0:*   LISTEN   2684/Xorg tcp6  0   0

Re: cannot open display: localhost:0.0

On 9/23/18 4:00 PM, Gene Heskett wrote: > On Sunday 23 September 2018 06:30:01 Étienne Mollier wrote: > > Maybe try: > > > > xhost +LOCAL: > > DISPLAY=localhost:0.0 xterm > > On which machine? The target of the ssh login, or this one >

Re: cannot open display: localhost:0.0

On Sunday 23 September 2018 10:36:01 Rob van der Putten wrote: Humm, my puzzle for X11Forwarding has even more pieces. copy/pasted from the konsole logged into the rock64, running stretch gene@rock64:~$ sudo netstat -anp|grep 6000 [sudo] password for gene: gene@rock64:~$ sudo netstat -anp|grep

Re: cannot open display: localhost:0.0

On Sunday 23 September 2018 09:20:34 Étienne Mollier wrote: > On 9/23/18 5:06 PM, Grzesiek Sójka wrote: > > $ xhost +LOCAL: ; DISPLAY=localhost:0.0 xterm > > non-network local connections being added to access control list > > xterm: Xt error: Can't open display: localhost:0.

Re: cannot open display: localhost:0.0

Hi there On 23/09/2018 13:48, Grzegorz Sójka wrote: I need to allow remote applications to connect to xorg. Since I log in using lxdm i have tcp_listen=1 in /etc/lxdm/lxdm.conf. Thus Xorg is running without -nolisten tcp flag. Unfortunately: $ xhost +localhost; DISPLAY=localhost:0.0 xterm

Re: cannot open display: localhost:0.0

Xorg > > is running without -nolisten tcp flag. Unfortunately: > > > > $ xhost +localhost; DISPLAY=localhost:0.0 xterm > > localhost being added to access control list > > xterm: Xt error: Can't open display: localhost:0.0 > > > > Any suggestions?? > > Mayb

Re: cannot open display: localhost:0.0

On 9/23/18 5:14 PM, Grzesiek Sójka wrote: > On 9/23/18 1:06 PM, Étienne Mollier wrote: > > ssh -YC user@remotehost > > I do not need encryption since all machines are in the same > network segment. So I prefer not to use ssh. In that case, perhaps you should simply test with remote clients; I

Re: cannot open display: localhost:0.0

On 9/23/18 5:06 PM, Grzesiek Sójka wrote: > $ xhost +LOCAL: ; DISPLAY=localhost:0.0 xterm > non-network local connections being added to access control list > xterm: Xt error: Can't open display: localhost:0.0 Whoops, however the DISPLAY=localhost:0.0 was a typo of mine. DISPLAY=:0.0 sh

Re: cannot open display: localhost:0.0

On 9/23/18 1:06 PM, Étienne Mollier wrote: On 9/23/18 2:59 PM, The Wanderer wrote: On 2018-09-23 at 10:24, Grzesiek Sójka wrote: On 9/23/18 10:30 AM, Étienne Mollier wrote: Maybe try: xhost +LOCAL: DISPLAY=localhost:0.0 xterm It does not work: # xhost +LOCAL; DISPLAY

Re: cannot open display: localhost:0.0

Étienne Mollier (2018-09-23): > or removing “-nolisten” to Xorg parameters: Finally somebody in this thread who payed attention in the last fifteen years... Regards, -- Nicolas George signature.asc Description: Digital signature

Re: cannot open display: localhost:0.0

On 9/23/18 2:59 PM, The Wanderer wrote: > On 2018-09-23 at 10:24, Grzesiek Sójka wrote: > > On 9/23/18 10:30 AM, Étienne Mollier wrote: > > > Maybe try: > > > > > > xhost +LOCAL: > > > DISPLAY=localhost:0.0 xterm > > > > It does not

Re: cannot open display: localhost:0.0

in /etc/lxdm/lxdm.conf. Thus Xorg is running without -nolisten tcp flag. Unfortunately: $ xhost +localhost; DISPLAY=localhost:0.0 xterm localhost being added to access control list xterm: Xt error: Can't open display: localhost:0.0 Any suggestions?? Maybe try: xhost +LOCAL: DISPLAY

Re: cannot open display: localhost:0.0

using lxdm i have tcp_listen=1 in /etc/lxdm/lxdm.conf. >>> Thus Xorg is running without -nolisten tcp flag. Unfortunately: >>> >>> $ xhost +localhost; DISPLAY=localhost:0.0 xterm >>> localhost being added to access control list >>> xterm: Xt error: Can't o

Re: cannot open display: localhost:0.0

tcp_listen=1 in /etc/lxdm/lxdm.conf. Thus Xorg is running without -nolisten tcp flag. Unfortunately: $ xhost +localhost; DISPLAY=localhost:0.0 xterm localhost being added to access control list xterm: Xt error: Can't open display: localhost:0.0 Any suggestions?? Maybe try: xhost +LOCAL

Re: cannot open display: localhost:0.0

in >>> using lxdm i have tcp_listen=1 in /etc/lxdm/lxdm.conf. Thus Xorg is running >>> without -nolisten tcp flag. Unfortunately: >>> >>> $ xhost +localhost; DISPLAY=localhost:0.0 xterm >>> localhost being added to access control list >

Re: cannot open display: localhost:0.0

: $ xhost +localhost; DISPLAY=localhost:0.0 xterm localhost being added to access control list xterm: Xt error: Can't open display: localhost:0.0 Any suggestions?? Maybe try: xhost +LOCAL: DISPLAY=localhost:0.0 xterm It does not work: # xhost +LOCAL; DISPLAY=localhost:0.0 xterm

Re: cannot open display: localhost:0.0

On 9/23/18 1:48 PM, Grzegorz Sójka wrote: > Hi there, > > I need to allow remote applications to connect to xorg. Since I log in using > lxdm i have tcp_listen=1 in /etc/lxdm/lxdm.conf. Thus Xorg is running without > -nolisten tcp flag. Unfortunately: > > $ xhost +localho

cannot open display: localhost:0.0

Hi there, I need to allow remote applications to connect to xorg. Since I log in using lxdm i have tcp_listen=1 in /etc/lxdm/lxdm.conf. Thus Xorg is running without -nolisten tcp flag. Unfortunately: $ xhost +localhost; DISPLAY=localhost:0.0 xterm localhost being added to access control list

Roundcube creates new user with host FQDN instead of localhost

Debian Stretch, roundcube 1.2.3+dfsg.1-4+deb9u1 Roundcube has created new user_id, with mail_host as FQDN and not localhost as previously. last_login with user where mail_host is localhost was 21. March, today login is mail_host FQDN. Can I fix this in the database so address books etc

Re: error: 'Access denied for user 'root'@'localhost' (using password: NO)'

On Sun, 26 Nov 2017 19:11:23 +0100 Ulf Volmer <u.vol...@u-v.de> wrote: > On 26.11.2017 18:48, Rainer Dorsch wrote: > > > root@scw:/etc/logrotate.d# cat /etc/mysql/debian.cnf > > # Automatically generated for Debian scripts. DO NOT TOUCH! > > [client] > > host

Re: error: 'Access denied for user 'root'@'localhost' (using password: NO)'

On 26.11.2017 18:48, Rainer Dorsch wrote: > root@scw:/etc/logrotate.d# cat /etc/mysql/debian.cnf > # Automatically generated for Debian scripts. DO NOT TOUCH! > [client] > host = localhost > user = root > password = > socket = /var/run/mysqld/mysqld.sock >

Re: error: 'Access denied for user 'root'@'localhost' (using password: NO)'

On Sonntag, 26. November 2017 17:01:23 CET Joe wrote: > On Sun, 26 Nov 2017 16:35:24 +0100 > > Ulf Volmer <u.vol...@u-v.de> wrote: > > On 26.11.2017 15:57, Rainer Dorsch wrote: > > > mysqladmin: connect to server at 'localhost' failed > > > error: 'A

Re: error: 'Access denied for user 'root'@'localhost' (using password: NO)'

On Sun, 26 Nov 2017 16:35:24 +0100 Ulf Volmer <u.vol...@u-v.de> wrote: > On 26.11.2017 15:57, Rainer Dorsch wrote: > > > mysqladmin: connect to server at 'localhost' failed > > error: 'Access denied for user 'root'@'localhost' (using password: > > NO)' error: e

Re: error: 'Access denied for user 'root'@'localhost' (using password: NO)'

On 26.11.2017 15:57, Rainer Dorsch wrote: > mysqladmin: connect to server at 'localhost' failed > error: 'Access denied for user 'root'@'localhost' (using password: NO)' > error: error running shared postrotate script for '/var/log/mysql/mysql.log / > var/log/mysql/mysql-slow.log /v

error: 'Access denied for user 'root'@'localhost' (using password: NO)'

Hello, I get (daily :-) mails from my cron.daily with the content Cron <root@scw> test -x /usr/sbin/anacron || ( cd / && run-parts --report / etc/cron.daily ) /etc/cron.daily/logrotate: mysqladmin: connect to server at 'localhost' failed error: 'Access denied for user 'ro

web site problems on localhost

Greetings; I found the problem, something had replaced the index.html, which was a link to the front-page.html of my web site with the default apache index.html. Restored that by rm'ing the renamed copy of it, then cp'd the ~ version back to the real one, voila! Web page functions normally.

Re: how to force mysql to use the name of my machine instead of localhost

t; > *Look at this: * > > > > *my count is lite@lite* > > *and hostname gives * > > *lite@lite:/opt/lampp$ hostname* > > *lite.umbb.dz <http://lite.umbb.dz>* > > > > > > *bin/mysql* > > > > *ERROR 1045 (28000): Acces s denied

Re: how to force mysql to use the name of my machine instead of localhost

$ hostname* > *lite.umbb.dz <http://lite.umbb.dz>* > > > *bin/mysql* > > *ERROR 1045 (28000): Acces s denied for user 'lite'@'localhost' (using > password: YES)* > > *Here it tries to connect as 'lite'@'localhost', I am > not 'lite'@'localhost', but lite@li

Re: Re: how to force mysql to use the name of my machine instead of localhost

> > > *bin/mysql* > > *ERROR 1045 (28000): Acces s denied for user 'lite'@'localhost' (using > password: YES)* > > *Here it tries to connect as 'lite'@'localhost', I am > not 'lite'@'localhost', but lite@lite* > *then same thing as root, even if use -h option : * &g

Re: Re: how to force mysql to use the name of my machine instead of localhost

*Thanks for reply and links* *But I am sure, the problem is in mysql.* *Look at this: * *my count is lite@lite* *and hostname gives * *lite@lite:/opt/lampp$ hostname* *lite.umbb.dz <http://lite.umbb.dz>* *bin/mysql* *ERROR 1045 (28000): Acces s denied for user 'lite'@'localhost'

Re: Re: how to force mysql to use the name of my machine instead of localhost

Abdelkader Belahcene wrote: > thanks a lot for any idea This has nothing to do with mysql or debian, but with wordpress. Please refer the manual or subscribe to the wordpress list. Perhaps someone else here may help you, but it would be OT IMO. regards

Re: how to force mysql to use the name of my machine instead of localhost

On 04/11/2017 07:45 AM, Abdelkader Belahcene wrote: Thanks for reply; I give more details. I install wordpress on my machine, it works fine on local, I mean i if write in the browser localhost/wordpress, it 's OK. I can use myIP/worpress on a remote machine to connect my server, It seems

Re: Re: how to force mysql to use the name of my machine instead of localhost

Thanks for reply; I give more details. I install wordpress on my machine, it works fine on local, I mean i if write in the browser localhost/wordpress, it 's OK. I can use myIP/worpress on a remote machine to connect my server, It seems working fine, I get the main page, BUT, CSS files

Re: how to force mysql to use the name of my machine instead of localhost

On Mon, 10 Apr 2017 07:51:56 +0100 Abdelkader Belahcene <abelahc...@gmail.com> wrote: > My machine has another name than localhost like lite.bela.umbb, > when I install mysql, it always takes the the localhost as the name > of the machine. this yields in a problem for

Utilisation du nom de la machine et non pas localhost par mysql

Bonjour tout le monde J ai un probleme d'installation de mysql, Il prend toujours le nom localhost bien j'ai donné, un nom a ma machine hostame ---> donne G580 hostname -f --> G580.enst.dz mais la connection dans mysql, le nom utiliser dans la base et "localhost" et

how to force mysql to use the name of my machine instead of localhost

My machine has another name than localhost like lite.bela.umbb, when I install mysql, it always takes the the localhost as the name of the machine. this yields in a problem for me, when I use for example wordpress and I want a remote connection. because the localhost stored in DB is irrelevant

Re: root@localhost mail not forwarding in Exim

Yes, this indeed was the problem! For some reason the mail was being sent to "user" even though I had no user named that. Thanks a bunch! I have had this problem for quite a while and never could figure out how to fix it. On Thu, Mar 2, 2017 at 5:34 AM, Bonno Bloksma wrote:

RE: root@localhost mail not forwarding in Exim

Hi, >[] > so, if I want to use mail.example.com as my fqdn, and the old fqdn was > something.else and r...@something.else was redirecting mail to > m...@something.else ... then what do I need to change in Exim to make this > happen? Is it maybe the aliases setting? Probably you edited

Re: root@localhost mail not forwarding in Exim

Have you tried sudo dpkg-reconfigure exim4-config Which Settings you have there? Am 01.03.2017 um 21:40 schrieb Jiangsu Kumquat: > I changed my server name and fqdn and now the mail to root@localhost is > bouncing. > > I went into every file that had the old name and changed it to

root@localhost mail not forwarding in Exim

I changed my server name and fqdn and now the mail to root@localhost is bouncing. I went into every file that had the old name and changed it to the new name but it still doesn't work. I did "grep -r something.else /etc" to find all the files. so, if I want to use mail.example.com

root@localhost mail not forwarding in Exim

I changed my server name and fqdn and now the mail to root@localhost is bouncing. I went into every file that had the old name and changed it to the new name but it still doesn't work. I did "grep -r something.else /etc" to find all the files. so, if I want to use mail.example.com

Re: sending authorized_keys to localhost from an account being created with adduser --disabled-password [was] Re: Need a tutorial

id private part, which the host account (test) can check). The ssh-agent is just in charge of keeping unlocked private keys around so that you only have to unlock them with your passphrase once per session. > My great mistake was to think that localhost, although being on the same > machin

Re: sending authorized_keys to localhost from an account being created with adduser --disabled-password [was] Re: Need a tutorial

the way, when I logged in via ssh (to *test*) now I was greeted by "Last login [time of my connection attempt]from localhost". So, I understand that I had logged into *test* via su - test and then had connected to *test* (from *test*) via localhost using ssh! Is this interpretation correct? Thanks to both of you again. Stephan

Re: sending authorized_keys to localhost from an account being created with adduser --disabled-password [was] Re: Need a tutorial

ser --disabled-password >> What do I want to do? >> I'd like to login to this account "test" from my normal user account by >> ssh via pubkey authentication. My (normal) user account has its keys >> generated and properly deposited on localhost. I logged into th

Re: sending authorized_keys to localhost from an account being created with adduser --disabled-password [was] Re: Need a tutorial

Stephan Beck: > Thanks, Greg. I trimmed your message just to let you know that it does > not work. To be clear: after having found my solution I did your test (only the test reproduced at the end of your message) and my solution does not work. Thanks Stephan

Re: sending authorized_keys to localhost from an account being created with adduser --disabled-password [was] Re: Need a tutorial

Thanks, Greg. I trimmed your message just to let you know that it does not work. Greg Wooledge: > On Fri, Sep 23, 2016 at 12:31:00PM +, Stephan Beck wrote: > As user stephan, to test that it works: > > stephan@hostname:~$ ssh test@localhost id > > If your username isn't

Re: RESOLVED Re: sending authorized_keys to localhost from an account being created with adduser --disabled-password [was] Re: Need a tutorial

Hi, Stephan Beck: > Hi > > Stephan Beck: >> Hi >> >> to...@tuxteam.de: >>> On Thu, Sep 22, 2016 at 03:35:00PM +, Stephan Beck wrote: >>> >>> > >> How do I get this public key onto localhost? > > No need to reply, I'l

Re: sending authorized_keys to localhost from an account being created with adduser --disabled-password [was] Re: Need a tutorial

d other chimed in with sage advice. > > > > Well, I have another one :-), a question, not a solution yet. > > > I have created a new user account with > adduser --disabled-password > What do I want to do? > I'd like to login to this account "test" fr

RESOLVED Re: sending authorized_keys to localhost from an account being created with adduser --disabled-password [was] Re: Need a tutorial

Hi Stephan Beck: > Hi > > to...@tuxteam.de: >> On Thu, Sep 22, 2016 at 03:35:00PM +, Stephan Beck wrote: >> >> > How do I get this public key onto localhost? No need to reply, I'll send the answer to document my solution within minutes. Stephan

Re: sending authorized_keys to localhost from an account being created with adduser --disabled-password [was] Re: Need a tutorial

mal) user account has its keys > generated and properly deposited on localhost. I logged into the account > "test" via su - test, creating a keypair. Fine. Typically, you want to create the keypair as the user on the machine which will be the client. This way the private key never

sending authorized_keys to localhost from an account being created with adduser --disabled-password [was] Re: Need a tutorial

to login to this account "test" from my normal user account by ssh via pubkey authentication. My (normal) user account has its keys generated and properly deposited on localhost. I logged into the account "test" via su - test, creating a keypair. Fine. How do I get this public ke

Re: localhost sin acceso

Ok, el problema esta parcialmente resuelto tengo acceso a localhost, pero ahora no puedo entrar a nada que este en var/www/ El 8 de febrero de 2016, 09:41, Camaleón<noela...@gmail.com> escribió: > El Sun, 07 Feb 2016 13:53:43 -0500, Ricardo Mendoza escribió: > > (ese formato...

Re: localhost sin acceso

t; > Saludos, tengo un problema hace ya un buen tiempo, abrí un hilo en >> > esta lista pero ha pasado mucho tiempo desde aquella ocasión y hasta >> > ahora puedo volver a retomar el tema por lo que quedo inconcluso, no >> > logro poner de nuevo en funcionamiento el

Re: localhost sin acceso

no logro > poner de nuevo en funcionamiento el acceso al localhost, al intentar > entrar por el url del nevagador me dice que no tiene acceso,podrían > ayudarme con orientación para solucionar este problema,gracias. Lo recuerdo, te respondimos varios y no llegaste a contestar el último

Re: localhost sin acceso

uedo inconcluso, no logro poner de > nuevo en funcionamiento el acceso al localhost, al intentar entrar por el > url del nevagador me dice que no tiene acceso,podrían ayudarme con > orientación para solucionar este problema,gracias. Muestra el /etc/hosts y la configuración de apache.

localhost sin acceso

Saludos, tengo un problema hace ya un buen tiempo, abrí un hilo en esta lista pero ha pasado mucho tiempo desde aquella ocasión y hasta ahora puedo volver a retomar el tema por lo que quedo inconcluso, no logro poner de nuevo en funcionamiento el acceso al localhost, al intentar entrar por el url

Re: localhost sin acceso

ncluso, no logro poner de nuevo en funcionamiento el acceso al localhost, al intentar entrar por el url del nevagador me dice que no tiene acceso,podrían ayudarme con orientación para solucionar este problema,gracias. Buenas, enseñanos tu fichero /etc/hosts

Re: localhost sin acceso

127.0.0.1 localhost 192.168.1.100 mymaquina.algo.net mymaquina # ::1 localhost ip6-localhost ip6-loopback fe00::0 ip6-localnet ff00::0 ip6-mcastprefix ff02::1 ip6-allnodes ff02::2 ip6-allrouters Bueno desinstale al apache y lo volví a instalar

Re: localhost sin acceso

El día 7 de febrero de 2016, 20:19, Ricardo Mendoza <pgsql...@gmail.com> escribió: > 127.0.0.1 localhost > 192.168.1.100 mymaquina.algo.net mymaquina > # > ::1 localhost ip6-localhost ip6-loopback > fe00::0 ip6-localnet > ff00::0 i

Re: localhost sin acceso

tiempo desde aquella ocasión y hasta ahora > puedo > > volver a retomar el tema por lo que quedo inconcluso, no logro poner de > > nuevo en funcionamiento el acceso al localhost, al intentar entrar por el > > url del nevagador me dice que no tiene acceso,podrían ayudarme con &g

Re: localhost sin acceso

> qualified domain name, using ::1. Set the 'ServerName' directive >> > globally to suppress this message >> >> Lo que te dice el mensaje es que tienes que definir la directiva >> "ServerName", que tendrás que añadir en el archivo que hayas usado para >> c

Re: localhost sin acceso

] [mpm_event:notice] [pid 1253:tid 3073447744] AH00489: Apache/2.4.10 (Debian) configured -- resuming normal operations [Sun Aug 30 11:37:24.034294 2015] [core:notice] [pid 1253:tid 3073447744] AH00094: Command line: '/usr/sbin/apache2' con cat /etc/hosts 127.0.0.1localhost miweb.net localhost 192.168.0.1

Re: localhost sin acceso

: Corrijo el html y top-posting. El 29 de agosto de 2015, 12:48, Camaleón noela...@gmail.com escribió: El Sat, 29 Aug 2015 12:33:11 -0500, Ricardo Mendoza escribió: (ese html...) Saludos, hace un tiempo intente montar un servidor web, de ese intento quedo inutilizado localhost

localhost sin acceso

Saludos, hace un tiempo intente montar un servidor web, de ese intento quedo inutilizado localhost, como puedo volver a habilitar el acceso a localhost,gracias

Re: localhost sin acceso

Podría ser cosa del /etc/hosts/ y ver que tenga lo siguiente: 127.0.0.1 localhost El 29 de agosto de 2015, 12:33, Ricardo Mendoza pgsql...@gmail.com escribió: Saludos, hace un tiempo intente montar un servidor web, de ese intento quedo inutilizado localhost, como puedo volver

Re: localhost sin acceso

- Original Message - From: uriel antony ciau To: Ricardo Mendoza Cc: debian-user-spanish Sent: Saturday, August 29, 2015 1:43 PM Subject: Re: localhost sin acceso Podría ser cosa del /etc/hosts/ y ver que tenga lo siguiente: 127.0.0.1 localhost El 29 de agosto de 2015, 12:33

Re: localhost sin acceso

no tengo idea El 29 de agosto de 2015, 16:46, Walter Reverdito kronno...@gmail.com escribió: Esta permitido en el apache o en el .htaccess? El sáb., 29 de agosto de 2015 15:12, Ricardo Mendoza pgsql...@gmail.com escribió: el problema esta en el acceso a la direccion localhost en el url del

Re: Localhost

On 2015-01-30 22:33:57 +0100, andre_deb...@numericable.fr wrote: On Thursday 29 January 2015 15:03:45 Vincent Lefevre wrote: 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

Re: Localhost

On Thursday 29 January 2015 15:03:45 Vincent Lefevre wrote: 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

Re: Localhost

Le 30/01/2015 01:24, Vincent Lefevre a écrit : 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

Re: Localhost

for the correct resolution is that we don't mix up the localhost line with the foobar line. And the order of the line's entries is important, e.g. it must be: 127.0.0.1 foobar.bar.net foobar not 127.0.0.1 foobar foobar.bar.net » Mais l'auteur ne

  1   2   3   4   5   6   7   8   9   10   >