Depending on your networking environment and local DNS settings, you may encounter networking errors and DNS resolver issues.
To validate that DNS and networking settings are working correctly from within a Fleio container, run the``fleio info`` command. This connects to a couple of HTTPS URLs that Fleio is using, implicitly testing Docker DNS resolvers:
fleio info # ... # last lines of the output: Request to https://fleio.com/versions.txt succeeded. Request to https://licensing.fleio.com/ succeeded.
If DNS resolver and networking is working correctly, you will see success messages above. If requests fail, debug further based on the error messages.
If you have a custom MTU set on the host where Fleio is installed, you also need customize the MTU value for Docker containers.
To keep the Fleio Docker container images small and to follow best practices, containers do not include network
debugging utilities, like
telnet. The Fleio
utils container (which you can enter using
fleio bash command) include these, and many other handy utilities.
celery and other containers
that are actually used for Fleio’s main functionality do not include debugging tools.
Use the following commands to confirm that DNS resolver is working and outgoing network connections to the specified host are allowed:
# The following command enters the fleio-celery-1 Docker container, you can replace it with another Fleio container, # e.g. fleio-backend-1. docker exec -it fleio-celery-1 bash # Replace the host ('fleio.com') and TCP socket (443) with desired values to test. # Connect throws an error if it fails for any reason, otherwise "ok" is printed. python -c "import socket; socket.socket(socket.AF_INET, socket.SOCK_STREAM).connect(('fleio.com', 443)); print('ok')" # exit the container: exit
If a connection is successfully established to the specified host on the specified TCP port, you will get “ok” printed at the console. Otherwise, you will get an error. Some common errors are exemplified below.
If host can not be resolved to IP address, meaning that the DNS resolver is not working correctly in the container (or you used a host that does not have a record in the global DNS system), you will get:
Traceback (most recent call last): File "<string>", line 1, in <module> socket.gaierror: [Errno -2] Name or service not known
If target host refused the connection:
Traceback (most recent call last): File "<string>", line 1, in <module> ConnectionRefusedError: [Errno 111] Connection refused
Connection times out, possibly a firewall is preventing the connection:
Traceback (most recent call last): File "<string>", line 1, in <module> TimeoutError: [Errno 110] Connection timed out
After you fill in the details on the OpenStack settings CREDENTIALS tab press Test connection to see if credentials are working. Then by pressing Save & sync or Sync button all the OpenStack objects (projects, instances, volumes, networks etc.) from the Fleio database are reset and the list of objects with states is retrieved from OpenStack.
You can then go to Cloud > Instances and check list of instances (or volumes, or some other resource that you know has elements in OpenStack) and see if there are any objects present.
Fleio requires notification messages from the OpenStack’s internal RabbitMQ queue to update the cloud objects’ state in the Fleio database and for most of the pricing rules.
You can confirm that Fleio receives notifications by shutting down an existing instance and see the instance status being updated in Fleio. Follow these steps:
Go to Fleio
Sync OpenStack objects as described in section How to check if Fleio connects successfully to the OpenStack API
Assuming you have a running instance, shut it down
Wait a few seconds for the instance to reach the STOPPED state. If your instance still shows as RUNNING state in Fleio, while you can see the instance being
SHUTOFFin OpenStack (
openstack server list --all-projects), that means that notifications are not working.
These steps apply for other operations as well: create instance, but it never shows up in Fleio, while you can see it created in OpenStack, or instance start for a shutoff instance.
To repeat these steps, make sure you start from a synced database by pressing Sync on the OpenStack CREDENTIALS tab.
The checklist to have notifications working is:
you added add the RabbitMQ user for Fleio
you set the notification settings
For debugging purposes, you can also enable notification logging with Notifications logging settings and see in the log file what notifications are received.
See in this video how notifications log should work:
If some notifications are received by Fleio and some are not received, see Some OpenStack notifications are not received.
For general OpenStack notifications troubleshooting, especially if none of the OpenStack notifications are received, see How to check if OpenStack notifications are working.
If just some notifications are not received, here are two possible reasons:
You have the same “Notifications pool name” (in OpenStack settings, Notifications tab) configured in two different Fleio installations that are connected to the same RabbitMQ. In this case, half of the notifications would go to one Fleio installation and the other half to the second installation. To fix this, just fill in another, unique “Notifications pool name” (it will be automatically created in RabbitMQ).
If “AMQP durable queues” checkbox is checked (in the staff panel > Settings > OpenStack, on the NOTIFICATIONS tab), about 33% of the notifications are not received. Make sure that AMQP durable queues checkbox is unchecked.
On Fleio install, upgrade or when running
fleio license to set a new license key, you may get an error:
* Setting license Error: License setting failed. Aborting ... Use 'fleio license' command to set a new license
Your license key may be bound to another Fleio installation. If you are in one of the following cases:
you have used the license key before and you are now performing a new Fleio installation,
you have changed the domain name on which Fleio is installed,
or you have changed the Django
SECRET_KEYin the settings.py file
you exceed the licensed amount of RAM on your OpenStack compute nodes or, in case of Fleio Hosting Billing Edition or Full Edition, you exceed the number of licensed clients
then contact the Fleio support department to reset your license.
Another possible reason for failing to set the license key is networking or DNS resolver issues in Docker containers. See How to test if DNS resolver and network connections are working from a container?.
To check if your Fleio installation is able to send email messages, try to reset a staff user’s password.
Go to the Fleio staff panel, log out first if you are logged in, and go to the login form (/staff URL). Click on the Forgot password link and fill in an email address of an existing staff user. If email settings are working correctly, you will receive a reset password email message.
If you do not receive a reset password email message, log in to the staff panel and check Utilities > Email message log. You should see Password reset entry marked with a red bar if email sending failed. Click on the entry and check “Error:” line on screen. Fix the email settings according to Email Settings and test reset password again.
If you can’t see a Password reset entry in the Email message log, double check that you used a valid staff user email address.
Make sure the mail server pipe is correctly configured.
You can also enable logging for incoming ticketing system emails. Once logging is enabled, if no emails are logged, it’s probably a misconfiguration on the mail server pipe.
Fleio database must be created with utf8mb4 character set. You can check the character set by running the following query on your database (usually fleio):
fleio mysql SELECT @@character_set_database, @@collation_database;
If your database contains tables that are using a different character set you will have to update the tables to have the UTF8mb4 set. This can be done with the following steps:
Export current DB
cd /home/fleio/compose db_pass=$(cat /home/fleio/compose/secrets/.db_password) docker compose exec -T db mysqldump fleio -u fleio -p"$db_pass" > fleio`date +%d.%m.%Y`.sql
Adjust the dump so all the
CREATE TABLEstatements will use utf8mb4.
Import the database (replace the path to your FIXED_DB with the proper name)
sudo chown fleio /home/fleio/compose/FIXED_DB.sql sudo -i -u fleio cd /home/fleio/compose # stop all services docker compose stop # and start just the database service docker compose start db # get the database password in a variable db_pass=$(cat /home/fleio/compose/secrets/.db_password) # enter the mysql console docker compose exec db mysql -u fleio -p"$db_pass" # once in console, drop the existing database and create a new one: DROP DATABASE fleio; CREATE DATABASE fleio CHARACTER SET utf8mb4 COLLATE utf8mb4_unicode_ci; # exit the console to Bash exit # import the database cat fleio.sql | docker compose exec -T db mysql fleio -u fleio -p"$db_pass"
Apply migrations by running
fleio django migrate
When you create an instance, as staff user or end-user, no network is shown or a network is missing from the Network selection dropdown.
By default, Network selection drop down includes:
OpenStack networks that are marked as
the client’s own networks
The fix may simply be to mark some network(s) as
Only networks that have at least one subnet are shown in the create instance form.
The Network selection field may be hidden or may have some networks pre-selected depending on the frontend settings.
Network included in the Network selection dropdown field also depend on weather
toggles are enabled or disabled.
If you’re in a development environment (not a production server) you can also enable debugging from settings.py file to get more information in browser when you’re accessing an invalid URL and in case an error occurs during development:
DEBUG = True
Now you’ll be able to see the backend API nicely formatted and even perform POST, PUT, and DELETE requests. Note that you need to be authenticated as
Here’s an example of PHP code calling the Fleio API: https://github.com/fleio/fleio-whmcs.
You can also run Django commands from the command line after you activate the Fleio Python virtual environment and move to the Django project directory. Please see Command line interface.
For more information regarding the Django command line see https://docs.djangoproject.com/en/dev/ref/django-admin/
Data points might take some time to be added, so you might want to wait for at least 30 minutes to 1 hour after the instance was deployed before starting to troubleshoot this.
If no metrics are displayed for an instance first step will be to check Fleio backend logs.
If you find no errors in logs or BadRequest errors when retrieving metrics you should ensure gnocchi is installed and both gnocchi and Ceilometer are configured correctly for the instance’s region. See Ceilometer configuration for instructions on how to configure gnocchi and Ceilometer.
You need the
bc system package (bash command line calculator). Here’s how you install it on Debian or Ubuntu:
sudo apt install bc
Other Linux distributions have similar commands to install
You periodically see “504 Gateway Timeout” toast messages in the web interface and when you check
docker logs fleio-backend-1), you see uWSGI restarting every few seconds. This may be caused by incorrect
system time on the Fleio server. Make sure you keep system time up-to-date.
When you try to secure a user account by enabling two-factor authentication you get error “Verification code is invalid” . Try a couple of times and even scan the QR code again and retry. If it still doesn’t work, and you made sure you are using the right code from Google Authenticator (or other application), then this may be caused by incorrect system time on the server where Fleio is installed. Make sure you keep system time up-to-date.