How to leave behind the welcome page and switch to a Production environment

I’ve installed OnlyOffice DocumentServer using the Docker Compose file here (installed on a linux-based NAS): github .com/ONLYOFFICE/Docker-DocumentServer/blob/master/docker-compose.yml (yes, I broke the link on purpose - apparently as a new poster I can’t have more than 2 in a post yet).

I un-commented and enabled all of the JWT environment settings and left them as-is. It installed perfectly, without any issues.

I was very impressed with the application after testing with the ds-example provided and am excited to flip the ‘switch’ to production mode. However, I cannot seem to find a way to do turn off the ‘welcome’ page with the testing notice listed.

I have searched these forums/GitHub/YouTube/Reddit and everywhere else (random tech blog sites) and have only found these two suggestions from 2022, which no longer work:

I’ve tried the steps from those posts and I either get a 404 error or a /GET error.

I am using a reverse proxy (Zoraxy) and it pulls up just fine with my LetsEncrypt SSL cert. My only issue is that I can’t get around the /welcome page. How has everyone here (using Docker compose) gotten around this issue? What am I missing?

Any and all advice would be appreciated, thank you!

Hi @StealthyDruid , welcome to the community!

That welcome page isn’t a test/production switch — it’s just a static landing page. Your integration will never touch it; apps talk to the Document Server API directly. So nothing about it is keeping you in “test mode.”

Going to production simply means integrating Document Server with your app (Nextcloud, custom app, etc.).

If you want to remove or replace the welcome page, since you’re using Docker Compose, you can mount your own HTML file over the default one. Create your custom HTML on the host, then add a volume to your docker-compose.yml:

yaml

volumes:
  - ./welcome/main.html:/var/www/onlyoffice/documentserver-example/welcome/docker.html:ro

Then run docker compose up -d --force-recreate.

Please note: after Document Server updates, the internal path may change. You’ll need to verify and reapply after major updates.

Also, since you mentioned testing with ds-example — just make sure it’s disabled before going live.

Let us know how the integration goes! And feel free to stick around — your experience setting this up on a NAS could help others in the community down the line.

1 Like

Thank you @Nurullo! For both the answer and the welcome! :slightly_smiling_face:

I understand now. I was under the impression I could remove the welcome page and just use OnlyOffice as a stand-alone with login options for different users. I tested NextCloud and my initial impression was that it’s a bit ‘much’. It seemed a bit too much for my (and my friends) needs.

I’ll re-visit NextCloud and look into other applications that might suit our needs better. I’ll definitely disable the ds-example to prevent accidental usage, thanks for the reminder!

Once I find the right app to connect with, I’ll report back!

Thanks again for the insight. When looking at that welcome page, I had no idea it was a must to integrate with a secondary app. Maybe for the next release, it might be a good idea to put a blurb about expectations of using OnlyOffice as a stand-alone. :slight_smile:

1 Like

Glad it helped!

If NextCloud feels like too much, take a look at ONLYOFFICE DocSpace — it’s a collaboration platform with customizable rooms, flexible access permissions, and built-in document editors. You can start with a free cloud account or self-host it. Might be a better fit for a small group.

Looking forward to hearing how it goes!

1 Like

Reporting back!

Since I already had NextCloud installed (and just hadn’t messed with it because it’s so massive with configurations/setups)… I updated the container to the latest version and just took my time to poke around.

I found the apps area and saw the OnlyOffice integration option. I downloaded/enabled the integration, entered my OnlyOffice location/JWT secret and voila! I didn’t even have to restart the container.

The only thing I’ve noticed is that when I open a document for the first time with an account, it doesn’t load. I tested with a few accounts and I’ve had to shift-refresh the window and then the document will show the percentage wheel loading and then be available to view/edit. Honestly, if that’s the only bug, I’m ok with it.

I also noticed the availability of permission sharing through NextCloud and tested that too. It really works for our use case and so I think I’ll stick with NextCloud for now (since I finally have it working) and if I decide to move to another platform, I’ll revisit at that time.

I really appreciate you taking your time to point me in the ‘write’ direction! :wink: I really thought OnlyOffice could be used as a stand-alone, but now I understand why it’s integration only. If another application has already done the security checks/features, then why re-invent the wheel. Just use what’s already available and you’ll reach a wider audience than if you had just stayed stand-alone. So I get it now. I just wish I hadn’t been banging my head against a wall for the last few days. :sweat_smile:

Thank you again!!

1 Like

This topic was automatically closed 12 hours after the last reply. New replies are no longer allowed.