📔
Ridy Flutter
  • 💁Introduction
  • đŸ› ī¸Installation
    • Firebase
    • Server
    • Client
    • Web Application
    • Update
  • 🎨Configuration
    • Admin Panel's Logo and Branding
    • Show Directions
    • Map SDK
    • Measurement System
  • â„šī¸Usage
    • Setup
    • Financials
    • Marketing
    • Management
    • Fleets
    • Online Payments
    • Complaints
  • 🛟Support
    • FAQ
    • Issue
Powered by GitBook
On this page
  • What kind of web panel do I need?
  • My server app and dashboards are started correctly but I can't open them on the browser
  • I get error 403 when searching for a place or submitting an order
  • Server stopped working suddenly.
  1. Support

FAQ

What kind of web panel do I need?

Nothing. The app is based on Node.js so it does not depend on any PHP service (WHM, cPanel, Plesk, Apache, none of them has be installed on the server.). We highly recommend against trying to install ridy on a server that has those services installed.

My server app and dashboards are started correctly but I can't open them on the browser

This could happen if the firewall is not open for the ports used by the app for external connections for example you can open port 4000-4003 using these commands:

sudo firewall-cmd --zone=public --add-port=4000/tcp --permanent
sudo firewall-cmd --zone=public --add-port=4001/tcp --permanent
sudo firewall-cmd --zone=public --add-port=4002/tcp --permanent
sudo firewall-cmd --zone=public --add-port=4003/tcp --permanent
sudo firewall-cmd --reload
sudo ufw allow 4000
sudo ufw allow 4001
sudo ufw allow 4002
sudo ufw allow 4003
ufw reload

I get error 403 when searching for a place or submitting an order

This error specifically comes from Google maps servers in case the API key you have provided during the initial configuration is not eligible. Make sure the google project has a billing account attached, The necessary APIs are enabled in accordance with the documentation and Try with unrestricted API key to rule out the possiblity of having an incorrect restriction policy.

Server stopped working suddenly.

Most probable reason for this is system reboot. Some hostings might occasionally reboot their servers. In case of reboot following command would restart the app services

docker-compose up -d
PreviousComplaintsNextIssue

Last updated 11 months ago

🛟