After deploying the one-click script from the Marketplace, I was unable to connect to the server via terminal.

Have any plan to add Varnish + Nginx +Redis insted of Apache.
Because it will be more faster then Apache on WordPress.
cloudways also digitalocean Company now.
https://www.cloudways.com/en/performance.php

The Django droplet installs Postfix but there isn't any documentation in regard.
Should I use Postfix to send emails or for something else? Thank you.

when i try and enter the configuration for my jitsi server it is telling me the file is not there when i replace the default link with the link of the server hosting jitsi

While using JITSI installation. I followed all the instructions and selected YES whenever offered.

Getting error for:

prosodyctl register the-user jitsi-example.digitalocean.com the-password
I used my email, my domain and my password

The error is: (******* is my domain name)

A problem occurred while reading the config file /etc/prosody/prosody.cfg.lua

Error: /etc/prosody/conf.d/*******.cfg.lua:65: attempt to call global 'i' (a nil value)

More help on configuring Prosody can be found at https://prosody.im/doc/configure
Good luck!

My domain is showing JITSI and it is working.
I want to restrict meeting creation and hence above changes are very important

hosted at DigitalOcean

Brand new 1-click Plesk 18.0.48 on Ubuntu 22.04 and getting the below warnings. Why are they not up to date?

W: http://autoinstall.plesk.com/PMM_0.1.11/dists/jammy/InRelease: Key is stored in legacy trusted.gpg keyring (/etc/apt/trusted.gpg), see the DEPRECATION section in apt-key(8) for details.
W: http://autoinstall.plesk.com/pool/PSA_18.0.48_10183/dists/jammy/InRelease: Key is stored in legacy trusted.gpg keyring (/etc/apt/trusted.gpg), see the DEPRECATION section in apt-key(8) for details.
W: http://autoinstall.plesk.com/PHP74_17/dists/jammy/InRelease: Key is stored in legacy trusted.gpg keyring (/etc/apt/trusted.gpg), see the DEPRECATION section in apt-key(8) for details.
W: http://autoinstall.plesk.com/PHP80_17/dists/jammy/InRelease: Key is stored in legacy trusted.gpg keyring (/etc/apt/trusted.gpg), see the DEPRECATION section in apt-key(8) for details.

There is an issue with an incomplete instruction at the bottom of the 'Get Started' link that appears next to the one click Jitsi Server once deployed. Toward the bottom of the instructions it states:

Edit /etc/jitsi/jicofo/jicofo.conf by switching to a configuration like this

jicofo {

This shall enable users to enter the conference with and URL or the URL and a plain password that can be configured in the browser and is the same for all users. See Jitsi documentation for the details.

Switch to a configuration file with 'jicofo {' doesn't make any sense. Appears to be an incomplete statement or thought.

• What does work here is using:

sudo nano /etc/jitsi/jicofo/sip-communicator.properties

• This generates a new file in the Jicofo directory
• add a new line in the blank file: org.jitsi.jicofo.auth.URL=XMPP: withyoururl.com
• Save/Exit

The rest of the instructions worked fantastic. Thank you!

Add haveged to the standard set of apt-get packages in the packer template.

The current ubuntu 20.04 docker 1-click template can not run docker-compose reliably on the Digital Ocean Basic Regular Intel Droplet.

In my experience, docker-compose will regularly, silently lock up the droplet with no indication as to what is wrong.

This is due to lack of a sufficient entropy pool as described by Digital Ocean as far back as 2013.

While there are ways to interact with DO to customize the docker 1-click on a case-by-case basis, this is beyond the expected scope of someone new to working with DO.

While I personally think docker-compose should at least issue a warning and explanation, Docker's position is ~that this is an OS-level concern.

I'm not sure if this is an appropriate place for this issue. ( Please delete it if not )

After creating a new droplet on digital ocean from dokku image. The initial configuiration page is not displayed.

Expected Result:
see initial configuration page
( as per instructions https://dokku.com/docs/getting-started/install/digitalocean/ ( step 9 )

Actual Result:
displays default Welcome to NGINX page

After droplet creation, the sshd service is started, but an external ssh client will not connect. The web console can connect without a problem and after a reboot, external ssh connections can be established.

Hi, is there any roadmap for updated droplet 1-clicks for existing templates? I am specifically wondering about WordPress.

Update WordPress droplet image in the marketplace with WP fail2ban version 5. The plugin developer has made changes to the plugin, and the upgrade from version 4 to 5 requires extra configurations that are unclear. If you keep the plugin updated on the image, it would be much easier to use the security solution.
Also, when updating the WordPress image on the marketplace page, explain (if applicable) what the droplet owner should do if they will be transferring a website from an older DO droplet with fail2ban 4.x, but the fail2ban configuration was never modified by the owner. Also, explain THE STEPS the owner should take if the fail2ban configurations were modified, and now the plugin will be upgraded to version 5.

I’d like to propose an enhancement that could benefit both developers and businesses: adding Cattr to the DigitalOcean Marketplace.

What is Cattr?

Cattr is an open-source time tracking and project management tool specifically designed for software development teams. It streamlines workflows, improves productivity, and ensures accurate billing for client projects. By integrating Cattr into the DigitalOcean Marketplace, you can provide users with an easy way to manage their time and tasks directly within their Droplets.

Why Cattr?

Here are a few reasons why adding Cattr to the marketplace would be beneficial:

Seamless Integration: With a 1-Click App for Cattr, developers could set up time tracking and project management effortlessly. No manual installations or complex configurations required—just a single click to get started.

Efficient Time Management: Cattr allows users to track time spent on specific tasks, projects, or clients. By integrating it with DigitalOcean Droplets, developers can seamlessly manage their workloads without switching between different tools.

Billing Accuracy: For freelancers and agencies, accurate time tracking is crucial for billing clients. Cattr’s features, such as billable hours and detailed reports, ensure transparency and fairness in invoicing.

Collaboration: Teams working on joint projects can use Cattr to coordinate tasks, allocate resources, and monitor progress. Having it readily available in the marketplace would encourage collaboration among developers.

Adding Cattr to the DigitalOcean Marketplace would enhance the overall experience for developers, freelancers, and businesses. It aligns with DigitalOcean’s commitment to simplicity and efficiency, making it a win-win for everyone.

link : https://github.com/cattr-app/server-application

Thank you for considering this suggestion. I look forward to seeing Cattr become a valuable addition to the DigitalOcean ecosystem.

Hi,
I have installed jitsi server from digital ocean marketplace and normal video calling is working fine. But whitboard feature is missing.
I try to install it manually, software installation done, configuration done. But still whiteboard option wont appear during call.

I am using Ubuntu 22
one click app link: https://marketplace.digitalocean.com/apps/jitsi-server

kindly suggest me solutions,
Regards,

Installed server but when then go to the IP address of the droplet, it fails to connect. Tried several times.

It would be amazing to a packer for https://developers.eventstore.com/

digitalocean best cloud provider . Please digitalocean you are so big company please update your droplet-1-click script . love you

How To Use the Github Enterprise Edition 1-Click Install on DigitalOcean
Please add Github Enterprise Edition 1-Click Install

PHP 8.0 is now (as of November 2022) out of active support and only due to receive security updates until November 2023. Are there plans to upgrade to this to PHP 8.1 in the near future?

I created a new droplet from the Marketplace page and then connected to it via SSH and typed bash /var/complete-jitsi-setup.sh just like the MOTD says and it failed saying:

-------------------------
Updating the system
-------------------------
Hit:1 http://mirrors.digitalocean.com/ubuntu jammy InRelease
Hit:2 https://repos-droplet.digitalocean.com/apt/droplet-agent main InRelease                                   
Hit:3 http://mirrors.digitalocean.com/ubuntu jammy-updates InRelease                                            
Hit:4 https://repos.insights.digitalocean.com/apt/do-agent main InRelease                                       
Hit:5 http://mirrors.digitalocean.com/ubuntu jammy-backports InRelease                                          
Hit:6 http://security.ubuntu.com/ubuntu jammy-security InRelease    
Hit:7 https://download.jitsi.org stable/ InRelease
Reading package lists... Done
E: Could not get lock /var/lib/dpkg/lock-frontend. It is held by process 8493 (unattended-upgr)
N: Be aware that removing the lock file is not a solution and may break your system.
E: Unable to acquire the dpkg frontend lock (/var/lib/dpkg/lock-frontend), is another process using it?

-------------------------
Configuring Jitsi for your domain
-------------------------
E: Could not get lock /var/lib/dpkg/lock-frontend. It is held by process 8493 (unattended-upgr)
N: Be aware that removing the lock file is not a solution and may break your system.
E: Unable to acquire the dpkg frontend lock (/var/lib/dpkg/lock-frontend), is another process using it?
bash: /usr/share/jitsi-meet/scripts/install-letsencrypt-cert.sh: No such file or directory
processing prosody conf file: /etc/prosody/conf.avail/*.cfg.lua
sed: can't read /etc/prosody/conf.avail/*.cfg.lua: No such file or directory
Failed to restart prosody.service: Unit prosody.service not found.
Failed to restart jicofo.service: Unit jicofo.service not found.
Failed to restart jitsi-videobridge2.service: Unit jitsi-videobridge2.service not found.

https://marketplace.digitalocean.com/apps/lamp
Ubuntu 22.04 Support
PHP 8.1

Would be nice to have the dokku version updated

Hi,

When can we expect a LEMP based on 24.04, preferably with PHP 8.3?

Thanks!

I'm pretty lost in how you're supposed to configure jitsi to use jwt token authentication. I've modified the /etc/prosody/conf.avail/jitsi.mydomain.com.cfg.lua:

-- changed to token authentication
VirtualHost "jitsi.mydomain.com"
    authentication = "token"
    -- Properties below are modified by jitsi-meet-tokens package config
    -- and authentication above is switched to "token"
    app_id = "<appid>"
    app_secret = "<appsecret>"
    allow_empty_token = false
    asap_accepted_issuers = { "<appid>" }
    asap_accepted_audiences = { "jitsi" }
    asap_key_server = "file:///etc/prosody/keys/public.key"
    ...

-- added so guests can join
VirtualHost "guest.jitsi.mydomain.com"
    authentication = "anonymous"
    c2s_require_encryption = false

And /etc/jitsi/meet/jitsi.mydomain.com-config.js:

var config = {
    // Connection
    //

    hosts: {
        // XMPP domain.
        domain: 'jitsi.mydomain.com',

        // When using authentication, domain for guest users.
        anonymousdomain: 'guest.mydomain.com',

        // Domain for authenticated users. Defaults to <domain>.
        // authdomain: 'jitsi.mydomain.com',

        // Focus component domain. Defaults to focus.<domain>.
        // focus: 'focus.jitsi.mydomain.com',

        // XMPP MUC domain. FIXME: use XEP-0030 to discover it.
        muc: 'conference.' + subdomain + 'jitsi.mydomain.com',
    },

    // BOSH URL. FIXME: use XEP-0156 to discover it.
    bosh: 'https://jitsi.mydomain.com/' + subdir + 'http-bind',

   jwt: {
        // The issuer of the token.
        issuer: 'codo',

        // The audience of the token.
        audience: 'jitsi',

        // Public key (base64 encoded) to verify the JWT signature.
        publicUrl: '/etc/prosody/keys/public.key',

        // The JWT should also contain 'room' claim that specifies the MUC room name.
    },

Changes made after ChatGPT instructions, so I'm not sure if any of it is nonsense. When I browse the server I can now create a jitsi room without username and password, and get assigned moderator. I expect it to ask for a JWT token for authentication. Any ideas?

A community user just reported here that when creating a new Discourse server from the Marketplace they are unable to SSH to the server and they keep getting the following error despite waiting for quite long:

Please wait while we get your droplet ready...

I was able to replicate the issue a few times with different Droplet sizes.

Can this Note: in the "Getting started after deploying Docker" be the default setup?

Note: The default firewall for the Docker One-Click is UFW, which is a front end to iptables. However, 
Docker modifies iptables directly to set up communication to and from containers. This means that 
UFW won’t give you a full picture of the firewall settings. You can override this behavior in Docker by 
adding --iptables=false to the Docker daemon.

The assumption with DO is that things are set up for the best scenario for a developer out of the box, this seems like an easy win to go with better default security to start with.

As mentioned in the second paragraph on the Docker iptables docmentation "If you’re running Docker on a host that is exposed to the Internet...", you need to restrict IP tables. Newly created droplets on DO are always public, they always get an IPV4 address.

Example : https://github.com/digitalocean/droplet-1-clicks/blob/master/rails-20-04/template.json
"appiication_name": "Ruby on Rails",
"appiication_version": "6.0.3.4",
There some lines start as appiication.
If there is no error in these lines, the issue can be closed.

not working

I installed the Jitsi and beside few issues it was working.
Then I followed the instructions on how to add user and password and how to allow guest users without password.
Now the jitsi service is not reachable from the browser.
In the instructions this part confused me because the jicofo { was just that with nothing else. So it was not clear what changes needs to be made to the file.

Edit /etc/jitsi/jicofo/jicofo.conf by switching to a configuration like this

jicofo {

This shall enable users to enter the conference with and URL or the URL and a plain password that can be configured in the browser and is the same for all users.

Any advice would be appreciated