Portainer Templates logo

Portainer Templates

ProxiTok

Stack

Social

Use Tiktok with an alternative frontend, inspired by Nitter.

Configuration

Type
Compose
Platform
linux
Source
Repo

Template by xneo1·Source

Services

proxitok-redis

Configuration

Image
redis
Command
redis-server --save 60 1 --loglevel warning
Restart
on-failure:5

Image details

Pulls: 11.1B
User: stackbrew
Created: Jun 05, 2014
Updated: 9 days ago
Status: active

proxitok-signer

Configuration

Image
ghcr.io/pablouser1/signtok:master
Restart
on-failure:5

Image details

User: pablouser1

proxitok

Configuration

Image
ghcr.io/pablouser1/proxitok:master
Ports
9770:80
Volumes
/cache : /portainer/Files/AppData/Config/proxitok-cache
Env vars
LATTE_CACHE=/cacheAPI_CACHE=redisREDIS_HOST=proxitok-redisREDIS_PORT=6379API_SIGNER=remoteAPI_SIGNER_URL=http://proxitok-signer:8080/signature
Restart
on-failure:5

Image details

User: pablouser1

Standalone Install

Select an install method, to see config/commands for deploying ProxiTok

Installation method

Install on Portainer

Import all app templates into your Portainer instance, for easy 1-click deploys

  1. Ensure both Docker and Portainer are installed, and up-to-date
  2. Log into your Portainer web UI
  3. Under Settings → App Templates, paste the below URL
  4. Head to Home → App Templates, and the list of apps will show up
  5. Select ProxiTok, fill in any config options, and hit Deploy

Template Import URL

https://raw.githubusercontent.com/Lissy93/portainer-templates/main/templates.json
Show Me demo
Original stackfile

The compose file this template deploys, straight from its repo:

services:
  proxitok-redis:
    image: redis
    command: redis-server --save 60 1 --loglevel warning
    container_name: ProxiTok-REDIS
    hostname: proxitok-redis
    mem_limit: 256m
    cpu_shares: 768
    security_opt:
      - no-new-privileges:true
    read_only: true
    user: 1026:100
    healthcheck:
      test: ["CMD-SHELL", "redis-cli ping || exit 1"]
    restart: on-failure:5

  proxitok-signer:
    image: ghcr.io/pablouser1/signtok:master
    container_name: ProxiTok-SIGNER
    hostname: proxitok-signer
    mem_limit: 512m
    cpu_shares: 768
    security_opt:
      - no-new-privileges:true
    read_only: true
    user: 1026:100
    healthcheck:
      test: wget --no-verbose --tries=1 --spider http://localhost:8080/ || exit 1
    restart: on-failure:5

  proxitok:
    image: ghcr.io/pablouser1/proxitok:master
    container_name: ProxiTok
    hostname: proxitok
    mem_limit: 1g
    cpu_shares: 768
    security_opt:
      - no-new-privileges:true
    healthcheck:
      test: stat /etc/passwd || exit 1
    ports:
      - 9770:80
    volumes:
      - /portainer/Files/AppData/Config/proxitok-cache:/cache
    environment:
      LATTE_CACHE: /cache
      API_CACHE: redis
      REDIS_HOST: proxitok-redis
      REDIS_PORT: 6379
      API_SIGNER: remote
      API_SIGNER_URL: http://proxitok-signer:8080/signature
    restart: on-failure:5
    depends_on:
      proxitok-redis:
        condition: service_healthy
      proxitok-signer:
        condition: service_healthy

Or deploy it directly from the source:

git clone https://github.com/xneo1/portainer_templates
cd portainer_templates
docker compose -f Template/Stack/proxitok.yml up -d

More install options in our documentation.

Container Documentation

proxitok-redis Documentation

Redis is the world’s fastest data platform for caching, vector search, and NoSQL databases.

Serve ProxiTok on your own domain behind Caddy, Nginx or Traefik. Fill in your domain and copy the result. It's a starting point, some apps need their own base URL or extra headers set too.

Proxying proxitok.example.com to http://proxitok:80

Add this to your Caddyfile

proxitok.example.com {
	reverse_proxy http://proxitok:80
}

Check the logs first

Nine times out of ten the logs tell you exactly what went wrong.

  • In Portainer, go to Containers, click the container, then Logs. Or run docker logs <container>
  • Exit codes help too: 137 means killed, usually out of memory. 126 or 127 means the command inside the image is broken.

Port already in use

If deployment fails with "Bind for 0.0.0.0:9770 failed: port is already allocated", something else on your server is using that port.

  • Find what's using it: sudo ss -tlnp | grep :9770
  • Stop the other service, or pick a different host port. In 9770:80 only the left number is yours to change, the right one belongs to the app.

Running but the page won't load

The container is up but nothing appears in your browser.

  • Use your server's real IP: http://your-server-ip:9770. The 0.0.0.0 link Portainer shows isn't a real address.
  • Give it a minute after first deploy, proxitok can take a while to initialise.
  • Make sure your firewall allows the port, e.g. sudo ufw allow 9770

Permission denied on volumes

If the logs show "permission denied", the app can't write to its data folder on the host.

  • Fix the ownership: sudo chown -R 1000:1000 /portainer/Files/AppData/Config/proxitok-cache

Image won't pull

Test the pull directly on the host: docker pull redis

  • "manifest unknown" means the tag no longer exists. This template uses latest, so try pinning a specific version instead.
  • "toomanyrequests" is the Docker Hub rate limit. Log in with docker login to raise it.
  • "no space left on device" means a full disk. Reclaim space with docker system prune

"exec format error"

This means the image was built for a different CPU architecture than your server.

  • Check yours with uname -m: x86_64 is amd64, aarch64 is arm64. Raspberry Pi and other ARM boards are the usual culprits.

Stack won't deploy

Compose stacks fail fast on small mistakes, and Portainer shows the reason just above the editor.

  • YAML only accepts spaces for indentation, a single tab breaks the whole file.

Raise an issue

Found something which isn't working as it should? Here's how to report it.

A Compose stack

ProxiTok is a Compose stack, a set of containers (3 of them) defined in one file and brought up together by Portainer, then started and stopped as a single app.

The services

This stack is built from 3 containers that run side by side. Here's each one, with the image it runs and anything it waits for first:

  • proxitok-redis runs redis
  • proxitok-signer runs ghcr.io/pablouser1/signtok:master
  • proxitok runs ghcr.io/pablouser1/proxitok:master, starts after proxitok-redis, proxitok-signer

Ports

A port is the door the app answers on. A mapping like 9770:80 means it's reachable on port 9770 of your server, where the left number is yours to change and the right one belongs to the app. Once it's running, open http://your-server-ip:9770 in a browser. It opens:

  • 9770:80, likely the web interface

Volumes

A volume is where ProxiTok keeps its files so they survive an update or a restart. Without one, anything it saves would sit inside the container and vanish the moment it's recreated. This template mounts:

  • /cache from /portainer/Files/AppData/Config/proxitok-cache on the host

Environment variables

Environment variables are the settings you hand over when you deploy, things like a password or a timezone. ProxiTok takes 6 of them, all with defaults you can leave alone or tweak:

  • LATTE_CACHE, defaults to /cache
  • API_CACHE, defaults to redis
  • REDIS_HOST, defaults to proxitok-redis
  • REDIS_PORT, defaults to 6379
  • API_SIGNER, defaults to remote
  • API_SIGNER_URL, defaults to http://proxitok-signer:8080/signature

Restart policy

The restart policy here is on-failure:5, so ProxiTok won't come back on its own after a crash or reboot. You bring it up again whenever you're ready. You can change this on the deploy screen. The choices are no (never restart), on-failure (only after a crash), unless-stopped (restart unless you stop it), and always (bring it back no matter what).

Networking

Portainer puts these services on one shared private network, so they can find each other by name (like proxitok-redis) while only the ports above are open to you.

Platform

The platform is linux, the kind of system the container is built to run on. Docker and Portainer handle this on a normal Linux server.

Portainer app templates

Zooming out, this whole page comes from a Portainer app template: a short recipe telling Portainer how to set ProxiTok up. Add the template list to Portainer once, then deploying ProxiTok is a click rather than a wall of config.