I do not have any errors in the log files for, nor _error.log, nor error.log.Ĭ_error.log does include this info AH01914: Configuring server :443 for SSL protocol When entering or, it instantly throws a server unavailable error, so it would seem that the reverse proxy isn't working (?). Whenever I make any changes, I restart rocketchat and apache2 services. The service file /lib/systemd/system/rvice is Īfter=network.target remote-fs.target nss-lookup.target nginx.target mongod.targetĮxecStart=/usr/local/bin/node /opt/Rocket.Chat/main.jsĮnvironment=MONGO_URL=mongodb://localhost:27017/rocketchat?replicaSet=rs01 MONGO_OPLOG_URL=mongodb://localhost:27017/local?replicaSet=rs01 ROOT_URL= PORT=3000 I have changed the URL in the settings to. All apache proxy mods are enabled (according to instructions). ![]() ![]() ServerAlias ServerAdmin /var/www/html/exampleĪlias /examplestaging /var/www/html/examplestagingĮrrorLog $ !=websocket Īll vhosts above are enabled. There are two Apache VirtualHosts for and, both enabled. has a website running on it with SSL and RocketChat needs to be at. FileAgo does not manage Rocket.I have successfully installed RocketChat on a private server, running Ubuntu 16.04, Apache 2.4, but I can't get SSL to work.īackground: The has existing LetsEncrypt ceritificates.The user details and password is synced with Rocket.chat upon every successful login.When a new user logs into FileAgo, his account is automatically created in Rocket.chat as well.Users in Rocket.chat is managed by FileAgo.Once activated, the users can click on “Chat” option on the top menu in their workspace to access chat area, and converse with other users in the organization. The chat is only activated if FileAgo manages to apply the required configuration successfully. Access token: The access token generated by Rocket.chatįileAgo will attempt to configure the Rocket.chat to use FileAgo authentication, and also configure some of its additional parameters.Admin user Id: The admin user id provided by Rocket.chat during creation of access token.Chat host URL (private): It should always be.Chat host URL: The value set in ROOT_URL of file chat_settings.env.Click on “Chat Server” from the left panel on the Admin Panel section and configure the following:.Login as admin user in FileAgo web portal.Logout from admin user account on Rocket.chat page.Ĭonfigure FileAgo to integrate with Rocket.chat.You will see a dialog box with a generated Token and user id.Type in “FileAgo access token” in the textbox and click on “Add”. ![]() You will need to create an access token for FileAgo to use In the “My Account” section, go to “Personal Access Tokens” section. ![]() From the top left menu, click on Admin user’s display picture icon and then “My Account”.Login to Rocket.chat as fileagoadmin user by browsing the ROOT_URL set in chat_settings.env.The Rocket.chat admin user ( fileagoadmin) and password was set during installation as per the details in chat_settings.env file. If you have started the chat server (which is listed as an optional step in the installation guide), then you already have a copy of Rocket.chat running alongside FileAgo Application Server. This document only applies if you have started chat server during installation.įileAgo offers an in-built chat, video and voice communication for users in an organisation by integrating with Rocket.chat.
0 Comments
Leave a Reply. |