Why I am always getting "inexistent-host" error? - ejabberd

I installed ejabberd 20.07 on Ubuntu and set domain name as faiqkhan-VirtualBox and set user-admin name as admin and password to 123456. I also check install.log file it shows
User admin#faiqkhan-VirtualBox successfully registered. I also checked using command ./ejabberctl registered_users faiqkhan-VirtualBox it returns my user name admin. I don't know why it always giving error Access of <<"admin#faiqkhan-VirtualBox">> from <<"::ffff:127.0.0.1">> failed with error: <<"inexistent-host">> while logging in.

After changing the given URL http://localhost:5280/admin/ to my host http://faiqkhan-VirtualBox:5280/admin/ I successfully logged in.

As the error message states the host (#domain) is non-existent.
You will need to add it to your ejabberd.yml under hosts e.g. for localhost:
hosts:
- "faiqkhan-VirtualBox"
- "localhost"
Or for admin#faiqkhan.com (username admin and hostname faiqkhan.com)
hosts:
- "faiqkhan-VirtualBox"
- "faiqkhan.com"
Cheers

Related

go-ethereum - geth - puppeth - ethstat remote server : docker: command not found

I'm trying to setup a private ethereum test network using Puppeth (as Péter Szilágyi demoed in Ethereum devcon three 2017). I'm running it on a macbook pro (macOS Sierra).
When I try to setup the ethstat network component I get an "docker configured incorrectly: bash: docker: command not found" error. I have docker running and I can use it fine in the terminal e.g. docker ps.
Here are the steps I took:
What would you like to do? (default = stats)
1. Show network stats
2. Manage existing genesis
3. Track new remote server
4. Deploy network components
> 4
What would you like to deploy? (recommended order)
1. Ethstats - Network monitoring tool
2. Bootnode - Entry point of the network
3. Sealer - Full node minting new blocks
4. Wallet - Browser wallet for quick sends (todo)
5. Faucet - Crypto faucet to give away funds
6. Dashboard - Website listing above web-services
> 1
Which server do you want to interact with?
1. Connect another server
> 1
Please enter remote server's address:
> localhost
DEBUG[11-15|22:46:49] Attempting to establish SSH connection server=localhost
WARN [11-15|22:46:49] Bad SSH key, falling back to passwords path=/Users/xxx/.ssh/id_rsa err="ssh: cannot decode encrypted private keys"
The authenticity of host 'localhost:22 ([::1]:22)' can't be established.
SSH key fingerprint is xxx [MD5]
Are you sure you want to continue connecting (yes/no)? yes
What's the login password for xxx at localhost:22? (won't be echoed)
>
DEBUG[11-15|22:47:11] Verifying if docker is available server=localhost
ERROR[11-15|22:47:11] Server not ready for puppeth err="docker configured incorrectly: bash: docker: command not found\n"
Here are my questions:
Is there any documentation / tutorial describing how to setup this remote server properly. Or just on puppeth in general?
Can I not use localhost as "remote server address"
Any ideas on why the docker command is not found (it is installed and running and I can use it ok in the terminal).
Here is what I did.
For the docker you have to use the docker-compose binary. You can find it here.
Furthermore, you have to be sure that an ssh server is running on your localhost and that keys have been generated.
I didn't find any documentations for puppeth whatsoever.
I think I found the root cause to this problem. The SSH daemon is compiled with a default path. If you ssh to a machine with a specific command (other than a shell), you get that default path. This does not include /usr/local/bin for example, where docker lives in my case.
I found the solution here: https://serverfault.com/a/585075:
edit /etc/ssh/sshd_config and make sure it contains PermitUserEnvironment yes (you need to edit this with sudo)
create a file ~/.ssh/environment with the path that you want, in my case:
PATH=/usr/bin:/bin:/usr/sbin:/sbin:/usr/local/bin
When you now run ssh localhost env you should see a PATH that matches whatever you put in ~/.ssh/environment.

Apache Geode Configuration

I had a problem trying to get Apache Geode (v1.0.0-incubating.M2) running on Linux.
The problem was: while I was trying to run gfsh start server --name=server1 example command from the documentation it gave me the following error:
Exception in thread "main" com.gemstone.gemfire.InternalGemFireError: Cannot resolve local host name to an IP address.
It turns out that you need to have your hostname (given by output of hostname command) be present in /etc/hosts file.
In my case, hostname gives an alias as an output (let's say my_alias), so I solved the problem by adding my_ip my_full_domain my_alias line to /etc/hosts.

Authentication error in freeradius server

I have installed freeradius server on Ubuntu-14.04, when I try take radtest on server using, radtest -x bob root123 127.0.0.1 1812 testing123
I get following error when I run freeradius -X,
[sql] User bob not found
++[sql] returns notfound >++[expiration] returns noop >++[logintime] returns noop >[pap] WARNING! No "known good" password found for the user. >Authentication may fail because of this. >++[pap] returns noop >ERROR: No authenticate method (Auth-Type) found for the request: >Rejecting the user >Failed to authenticate the user >Using Post-Auth-Type Reject
I have added user in users file, bob Cleartext-Password := "root123"
In eap.conf file, default_eap_type = peap
Still getting an error, can anyone help me to resolve my issue?
Have you enabled the text-file as a valid source for your users?
The error message seems like you just enabled sql but not the
#
# Read the 'users' file
files
in the sites-enabled/default (and innter-tunnel)
Hopefully this fixes your problem

Symfony2 and GoDaddy error message with incorrect information

I recently uploaded a Symfony2 project to GoDaddy and I'm having trouble accesing it because I get the message:
An exception occured in driver: SQLSTATE[HY000] [1045] Access denied for user 'root'#'127.0.0.1' (using password: NO)
Obviously the message is clear, so I checked and rechecked my parameters.yml, and the message don't even match what I have there, which I have changed several times to try to fix. This is my parameters.yml:
parameters:
database_driver: pdo_mysql
database_host: localhost
database_port: null
database_name: database1
database_user: database1user
database_password: mytestpassword
mailer_transport: smtp
mailer_host: 127.0.0.1
mailer_user: null
mailer_password: null
locale: en
secret: RandomTokenThatWillBeChanged
debug_toolbar: true
debug_redirects: false
use_assetic_controller: true
So, the error message doesn't tell me what is my real problem, or it is loading the parameters from some cached version that I haven't found yet. Any ideas of what else could cause or where could a cached version of this data be?
One of the best practice when developing a Symfony application is to
make it configurable via a parameters.yml file. It contains
information such as the database name, the mailer hostname, and custom
configuration parameters.
As those parameters can be different on your local machine, your
testing environment, your production servers, and even between
developers working on the same project, it is not recommended to store
it in the project repository. Instead, the repository should contain a
paramaters.yml.dist file with sensible defaults that can be used as a
good starting point for everyone.
Then, whenever a developer starts working on the project, the
parameters`.yml file must be created by using the parameters.yml.dist
as a template. That works quite well, but whenever a new value is
added to the template, you must remember to update the main parameter
file accordingly.
As of Symfony 2.3, the Standard Edition comes with a new bundle that
automates the tedious work. Whenever you run composer install, a
script creates the parameters.yml file if it does not exist and allows
you to customize all the values interactively. Moreover, if you use
the --no-interaction flag, it will silently fallback to the default
values.
http://symfony.com/blog/new-in-symfony-2-3-interactive-management-of-the-parameters-yml-file
So, is it not possible that your paramaters.yml is overwritten by paramaters.yml.dist?
You can also try to completely clear the cache
In Dev:
php app/console cache:clear
In Production:
php app/console cache:clear --env=prod --no-debug

Password Reset policy in OpenSSO

I had to implement Password Reset policy....For which I had OpenSSO deployed on Glassfish server and OpenDS as the Data Store...I followed Indira's blog...
Password Reset With OpenDS
And executed all commands....Since I did not configure SMTP, when I try to Reset the Password of a particular User (Note: I hav specified a Gmail ID as the email Address of that user) after answering the Question, I get confirmation saying
"Your password has been reset but we are unable to send it to you. Contact your administrator."
How do I configure SMTP in OpenSSO and OpenDS?
OpenDS (and OpenDJ, the continuing open source project) has some global properties to point to the SMTP server.
Note that it doesn't support authentication at this point.
$ dsconfig set-global-configuration-prop --port 4444 --hostname hostname --bindDN "cn=Directory Manager" --bindPassword password --set smtp-server:smtp.example.com --trustAll --no-prompt
Kind regards,
Ludovic
I just had this problem, so for the record I think it's probably because you need to replace <Password-Administrator> in the WEB-INF/classes/amPasswordResetModuleMsgs*.properties files with a real email address.
I found that my Authentication debug log file had this error in it:
ERROR: Could not send email to user [Ljava.lang.String;#30720e48
com.sun.mail.smtp.SMTPSendFailedException: 553 5.5.4 <Password-Administrator>... Domain name required for sender address Password-Administrator
;
nested exception is:
com.sun.mail.smtp.SMTPSenderFailedException: 553 5.5.4 <Password-Administrator>... Domain name required for sender address Password-Administrator
at com.sun.mail.smtp.SMTPTransport.issueSendCommand(SMTPTransport.java:2057)
I found the solution on the OpenAM mailing list originally: http://lists.forgerock.org/pipermail/openam/2012-April/005912.html
I used this sed command to do update all the files at once:
sed -i -e 's/\<Password-Administrator\>/user#address\.com\.au/g' amPasswordResetModuleMsgs*.properties