Hi @magletdinov,
You can download the release zip and unpack it by hand (simplest).
On any machine with internet access, download the nf-weblog-<version>.zip file from the GitHub releases page. You can also find it in the plugin registry website.
Copy the zip to the server and unpack it into the plugins folder. The folder name must be exactly <plugin>-<version>:
VER=1.1.1 # use the version you actually downloaded
mkdir -p $HOME/.nextflow/plugins/nf-weblog-$VER
unzip nf-weblog-$VER.zip -d $HOME/.nextflow/plugins/nf-weblog-$VER
The plugins folder is set by NXF_PLUGINS_DIR and defaults to $NXF_HOME/plugins, which is ~/.nextflow/plugins. Point that variable somewhere else if you want a shared location. Then pin the version and stop Nextflow from trying to download anything:
// nextflow.config
plugins {
id 'nf-weblog@1.1.1'
}
export NXF_OFFLINE=true # since 24.04 this also blocks plugin downloads; the version must be pinned
nextflow run main.nf -with-weblog http://your-endpoint
Check that the plugin version works with Nextflow 25.10.4. The Plugin-Requires line in META-INF/MANIFEST.MF inside the zip shows the minimum Nextflow version it needs.
Is there another way to install the plugin, please? Perhaps from the source code on GitHub?
Yes, you can build it from source on GitHub, but building needs internet access to download the Gradle dependencies and Nextflow libraries. Do it on a connected machine with Java 17 or newer:
git clone https://github.com/nextflow-io/nf-weblog.git
cd nf-weblog
git checkout <tag> # pick a release tag
make assemble # builds the plugin zip
# or: make install # puts it straight into ~/.nextflow/plugins on this machine
Then copy the zip (or the installed nf-weblog-<version>/ folder) to the server, the same way as in the first solution I gave. Building on the restricted server itself only works if you have an internal Maven/Gradle mirror. The only advantage over the first solution is that you can review or patch the code first.
There is still a third way, which is the best choice if you have many servers or users:
NXF_PLUGINS_REGISTRY_URL (added in 25.10) points Nextflow at a custom or private plugin registry instead of registry.nextflow.io.
NXF_PLUGINS_TEST_REPOSITORY points to a nf-weblog-X.Y.Z-meta.json file or a plugins.json index. You can host this on an internal web server, with its download URL pointing to your internal copy of the zip.
- A proxy or allowlist: if the server can go out through a proxy, set https_proxy/http_proxy, or allow registry.nextflow.io and the hosts that serve the downloads. Then nextflow plugin install nf-weblog@ works as normal.
I’d still go for the first solution, if it’s a single server.