I have succesfully installed openfire on centos7 with mariadb as database, and created a user to test chat username=mickey, password=mickey.
Centos machine on which openfire is installed with ip (192.168.1.141).
Now i have installed spark messenger on my windows laptop to test chat, but somehow i am unable to login.
As on windows i am successfully accessing admin console(192.168.1.141:9090).
But spark login is not working.
Spark is giving error "unable to verify certificate"
Under the 'advanced' link on the Spark login screen, there's an option that allows you to ignore the certificate warnings - that is the short answer.
The issue that you would ignore is a security-related (which you arguably should not ignore). When you installed Openfire, you were asked to provide an XMPP domain name (as well as the fully qualified domain name for the server on which Openfire is installed). These can, but should not be an IP address. Based on these values, Openfire will generate self-signed certificates, which are presented to Spark.
You should review your setup, and make sure that you properly defined your XMPP domain name (eg: example.com) and the FQDN for your server (eg: myserver.example.com). When both values differ, you should set up DNS records - the Openfire admin console will warn you of this, and will provide configuration for your specific setup.
As i was accessing openfire server that is installed in centos7 pc, on my windows pc(in which i have installed spark web app), spark was not connecting to centos server. I have to open these ports for public on centos, this helped me
firewall-cmd --zone=public --add-port=9090/tcp --permanent
firewall-cmd --zone=public --add-port=9094/tcp --permanent
firewall-cmd --zone=public --add-port=5222/tcp --permanent
firewall-cmd --zone=public --add-port=7777/tcp --permanent
Related
I have two separate clusters (Application and DB) in the same namespace. Statefulset for DB cluster and Deployment for Application cluster. For internal communication I have configured a Headless Service. When I ping from a pod in application cluster to the service it works (Works the other way round too - DB pod to service works). But sometimes, for example if I continuously execute ping command for like 3 times, the third time it gives an error - "ping: : Temporary failure in name resolution". Why is this happening?
As far as I know this is usually a name resolution error and shows that your DNS server cannot resolve the domain names into their respective IP addresses. This can present a grave challenge as you will not be able to update, upgrade, or even install any software packages on your Linux system. Here I have listed few reasons
1.Forgot configuring or Wrongly Configured resolv.conf File
The /etc/resolv.conf file is the resolver configuration file in Linux systems. It contains the DNS entries that help your Linux system to resolve domain names into IP addresses.
If this file is not present or is there but you are still having the name resolution error, create one and append the Google public DNS server as nameserver 8.8.8.8
Save the changes and restart the systemd-resolved service as shown.
$ sudo systemctl restart systemd-resolved.service
It’s also prudent to check the status of the resolver and ensure that it is active and running as expected:
$ sudo systemctl status systemd-resolved.service
2. Due to Firewall Restrictions
By some chance if the first solution did not work for you, firewall restrictions could be preventing you from successfully performing DNS queries. Check your firewall and confirm if port 53 (used for DNS – Domain Name Resolution ) and port 43 are open. If the ports are blocked, open them as follows:
For UFW firewall (Ubuntu / Debian and Mint)
To open ports 53 & 43 on the UFW firewall run the commands below:
$ sudo ufw allow 43/tcp
$ sudo ufw reload```
For firewalld (RHEL / CentOS / Fedora)
For Redhat based systems such as CentOS, invoke the commands below:
```$ sudo firewall-cmd --add-port=53/tcp --permanent
$ sudo firewall-cmd --add-port=43/tcp --permanent
$ sudo firewall-cmd --reload
I hope that you now have an idea about the ‘temporary failure in name resolution‘ error. I also found a similar git issue hope that helps
https://github.com/kubernetes/kubernetes/issues/6667
After install pgAdmin III from Ubuntu Software Center, I opened it and it required to add a connection to a server. So I filled in information as below:
Upon clicking on Ok Button, it showed the error message
Error connecting to the server: could not translate host name
"http://127.0.0.1" to address: Name or service not known
As message indicated, I thought the postgres service was not started. Therefore, I went on go terminal console and start service by entering sudo service postgresql start, but it returned Failed to start postgresql.service: Unit postgresql.service failed to load: No such file or directory.
. What's wrong or missing for my pgAdmin III? I'm just using Ubuntu earlier and I have never this problem on windows. Thanks.
http://127.0.0.1 is more a URL, that field is looking for a host so simply remove the http:// to leave the localhost's IP address 127.0.0.1 or type localhost if that resolves to the correct address (it should, usually, via /etc/hosts or the like)
Also, Debian/Ubuntu tend to ship the database servers separately. For Ubuntu, the postgresql package (which requires postgresql-common) package should include /lib/systemd/system/postgresql.service therefore you should be able to sudo systemctl start postgresql
Do you have postgresql (as opposed to postgresql-client) installed?
I am running a Django server on a redhat computer. I can remotely connect to the computer via ssh connection, so I am assuming there is no firewall issue. However, when I execute the following command (which supposedly should make the server publicly available)
python3 manage.py runserver 0.0.0.0:8080
The server is not reachable from any other computer. Locally (from the redhat machine itself) I can see the server is running.
I am new to redhat, so if there is any other information I should provide, please let me know.
So far, I have found that I can make my server reachable using localtunnel, however, since it changes the url, I prefer to solve the issue some other way.
UPDATE: the problem had nothing to do with Django. What made confusion was that the server was running with no problem and turned unreachable with no specific reason.
Anyways, I needed to add some configurations (found in here) to make port:8080 reachable.
Open the port 8080 with
firewall-cmd --zone=public --add-port=8080/tcp
To add it permanently to the system, add --permanent like so:
firewall-cmd --zone=public --add-port=8080/tcp --permanent
I installed VirtualBox on Windows 7, and created a virtual machine, where I installed CentOS 7. Then in CentOS 7 I installed CollabNet Subversion Edge, following this information as a guide and
performed all the steps provided there, but I can not access the server.
The installation should be performed on a desktop machine and the server I'm trying to access from a notebook, which is connected to the same network as the desktop machine. Also obviously, as the network has a proxy to surf, I had to configure it, and doing well because I can surf the internet and others. It's using 'Bridged Adapter' networking in the VM settings.
Can you think of any idea why I do not have access? Any help is welcome.
I found a response similar to what I'm looking for, but do not quite understand what it says. I'm only in CentOS7 enp0s3 interface, and there is collabnet running, not running on another interface.
NEWS:Gain access the server using its IP (172.x.x.x:3343/svn or 172.x.x.x:18080/svn), but not by name. Maybe there is a problem in the computer name, applies only to Windows, and CentOS running on the virtual machine, use another computer name. Can it be? If so, you know how to identify such equipment?
Looks like a firewall issue. Try to run following commands:
firewall-cmd --permanent --zone=public --add-port=<dst_port>/tcp
firewall-cmd --reload
Hope this helps
I have a Pi that runs hostapd and dhcpd on arch linux to create it's own land with the Pi's (routers) IP being 10.0.0.1. This uses the wlan0 interface and it only serves as a standalone router running a web server.
Once I connect to the Pi, I use 10.0.0.1 to display the web pages, but I want to use a hostname such as firepi. I have tried using dnsmasq, but I haven't been successful. Any help would be greatly appreciated especially if you can give me some detailed examples as I am a novice.
The purpose of this system is that I have created a web app that you can use to ignite fireworks over WiFi at a safe distance. I would just like the convenience of using a hostname instead of the IP address.
I must add that I will more than likely be using an iPhone to connect to the server, should this affect anything.
Not too sure how or why but this is what I did and it is successfully working now, so this is just for future users who may need a similar setup to mine.
First I installed hostapd and dhcpd and made sure they were working. Next I changed '/etc/hostname' to firepi and the '/etc/hosts' and added '10.0.0.1 firepi'. Then I installed dnsmasq, and set the interface to wlan0, and finally added '10.0.0.1 firepi' to '/etc/resolv.conf'.
After a full reboot, I joined the network on my iPhone, navigated to firepi and sure enough, it worked!
Thanks to the other users for their advice and tips.
You can use avahi on Arch as well to resolve your hostname:
sudo pacman -S avahi nss-mdns
Start the avahi daemon:
sudo systemctl enable avahi-daemon.service
sudo systemctl start avahi-daemon.service
Edit /etc/nsswitch.conf
sudo vim /etc/nsswitch.conf
Change the line:
hosts: files myhostname dns
to
hosts: files myhostname mdns_minimal [NOTFOUND=return] dns
Reboot
Note: don't forget to add .local to your hostname.
See also:
http://blog.pixxis.be/post/77285636682/resolve-hostname-with-arch-linux-on-a-raspberry-pi
If you just want to be able to use "firepi" as hostname to connect to it, you can simply add it to your /etc/hosts file using the syntax "IP host".
To make it as easy as possible, run this command as root:
echo "10.0.0.1 firepi" >> /etc/hosts
That'll do the trick.
Can you try avahi ?
sudo apt-get install avahi-daemon and
sudo apt-get install avahi-browse
I've successfully used that on Raspian. Unless you change the hostname using
sudo raspi-config you will access via raspberrypi.local
Note that if you plan to access the RPi from Windows you will need to install Bonjour Service first(if you have iTunes intalled, you might have those, run services.msc and check if the Bonjour Service is started)
Another note: On a friend's iphone I've installed a generic vnc client and had x11vnc running on the RPi and succesfully managed to connect to the RPi (since avahi-daemon was installed)