I have added a friend request (Add To Contact) with the following command.
sudo ejabberdctl add_rosteritem rohit localhost test localhost test none none
And While getting the contact it showing as below,
sudo ejabberdctl get_roster rohit localhost
ashwin#localhost ashwin#localhost both none
girish#localhost girish#localhost none out
test#localhost none none none none
But test#localhost is displaying neither in the "Pending contacts" nor in the "Contact Request" in Web client GUI for both rohit and test user.
Related
Recently I built a Self-Hosted GitLab Server, and it was working fine. However, after I updated the GitLab account's password, I was unable to pull image from registry container. I getting following error:
unauthorized: HTTP Basic: Access denied. The provided password or token is incorrect or your account has 2FA enabled and you must use a personal access token instead of a password.
Following is the command I run in my runner server after updated password
docker login gitlab.{name}.com:5050 -u {username} -p {password}
and the result returned from the command
Login Succeeded
After I change my GitLab account password to previous password, it working fine again. May I know why is this happening and how to resolve this?
Expected result will be able to pull image from registry container after updated password, previous password cache should be cleared.
I'my trying to simply register user using ejabberdctl:
ejabberdctl register admin 100.100.100.100 123456
and receive: unknown virtual host - same for every user.
Configuration:
ejabberd.yml:
hosts:
- "100.100.100.100"
auth_method:
-sql
-external
/etc/hosts
127.0.0.1 100.100.100.100
127.0.0.1 localhost
No errors in log files both in /opt/ejabberd/logs and /var/log/
No errors in debug mode.
ejabberd version - 21.07
I followed your configuration, with only this change (I don't have SQL or extauth configured):
auth_method:
- internal
And it works correctly:
ejabberdctl register admin 100.100.100.100 123456
User admin#100.100.100.100 successfully registered
Can you configure like I do, only internal, and check again?
If it works with internal, then enable only sql. Does it work?
If it works with sql, enable only external. Does it work?
If it works, then enable both sql and external as you desired. Does it work?
ejabberdctl register admin custom_hostname your_custom_password
it works and will create account like
hostname: admin#custom_hostname
password: your_custom_password
Trying to login to clasp on the Pixelbook. Can't: "This site can’t be reached localhost refused to connect.
Search Google for localhost 39133"
Am running the Node server. Can connect to localhost with Node via the command line, but cannot get the clasp login to connect to localhost.
Try:
clasp login --no-localhost
That will allow you to login without using the localhost server. You'll just have to do a couple more steps of copy/paste.
I am facing some issues while setting up my Synology DS218play. I hope you will be able to help me. Here is my current configuration :
I have a virtual host set with the Web Station app
Domain : blog.domain.com
Directory : web/blog.domain.com/wordpress/
HTTP Server : Nginx
PHP version : 7.0
HSTS and HTTP/2 checked
I have installed the MariaDB 10 and phpmyadmin packages from Synology Community repository.
I can log into phpmyadmin with root user, hence I created a blog user and a 'blog' database. blog user is granted with all privileges for blog database. I set localhost to hostname for blog user. I guess SQL Server is listening through 3306 port by default, I don't see where I can check or edit this.
I can log into phpmyadmin with my blog user, and I see only the blog database (and information_schema, I assume it is normal).
Here comes the problem : When I try to go to https://blog.domain.com, it redirects me to https://blog.domain.com/wp-admin/setup-config.php, I press 'Let's go!' and enter my credentials :
user : blog
password :
hostname : localhost
database name : blog
table prefix : wp_ (default value)
And when I validate, I go to an error page : error establishing a database connection. I triple checked user/password, it works into phpmyadmin and not with WordPress. So I assume the error comes from hostname, or phpmyadmin configuration to allow the connection from outside the phpmyadmin's interface. I would like to test directly on my NAS with mysql command line, but I have not found any solution to do that.
NB: I don't know if it is useful, but I set up my router to redirect the port 3306 to my NAS. It did not change anything.
Thank you for any help.
Using Apache instead of Nginx here, but I had the exact same problem on my Synology. It was solved by changing the hostname from localhost to 127.0.0.1:3307. This is the way to link to Maria DB 10. The port for Maria DB 5 would apparently be 3306 (not tested). Wordpress is now installed correctly and I can access the admin page.
But... this is not the end of the story. As soon as you will try to install a theme or a plugin, or update something, Wordpress will ask for FTP credentials to the Web Server. To make a long story short, Telnet your way as Default Admin (the SSH terminal and Admin Default User must be enabled) and type:
sudo su <--- To get root access
Use the same password
chown -R http:http /volume1/web/myfoldername <--- To give propre ownership
chmod -R 775 /volume1/web/myfoldername <--- To give propre access privileges
Everything works well from there.
I installed Redmine 2.6.1.1 using Bitnami on Win 7, but couldn't figure out why redmine cannot send any email. I edited the configuration.yml file under \redmine-2.6.1-1\apps\redmine\htdocs\config and tried to send a test mail via both Gmail and our own e-mail server, but it didn't work.
My configuration.yml file is just like below:
default:
email_delivery:
delivery_method: :smtp
smtp_settings:
enable_starttls_auto: true
address: smtp.gmail.com
port: 587
domain: smtp.gmail.com
authentication: :plain
user_name: "someusername#gmail.com"
password: "somepassword"
In this configuration the error is:
an error occurred while sending mail (a socket operation was attempted to an unreachable network. - connect (2))
If I change the address and domain values with IP addresses then the error becomes:
an error occurred while sending mail (Permission denied - connect(2))
If I try to configure it with the values of our own mail server, then I still get the second error (permission denied).
I tried it in another PC and it worked. However, the same configuration in the old PC, it does not work. 2 PCs are in the same network and the only difference between 2 installations is that I did not configure mail settings during the Bitnami installtion in the old machine. After the installation was completed, I modified configuration.yml. However, in the new PC, I configured it during the installation.
I could solve the problem finally. The reason is McAfee security. When I disable McAfee's "Access Protection" task, it worked without any problem.