search

linuxserver / docker-pairdrop

GNU General Public License v3.0
47 stars 4 forks source link

[BUG] devices do not show up in pairdrop #16

Closed back-lacking closed 4 months ago

back-lacking commented 4 months ago

Is there an existing issue for this?

Current Behavior

so currently i have pairdrop running behind traefik. however, my 2 devices cant see each other. they are both on the same network. I tried pairing them together, but they would show up as undefined on both sides image they are both in the same room. and they still dont show up

Expected Behavior

devices show up and im able to send devices

Steps To Reproduce

  1. use my docker compose file (ofc replacing pairdrop.local.domain with your domain)
  2. docker compose -d
  3. get 2 devices on the site
  4. see that neither devices see each other, even when being paired, or when in same room

Environment

- OS: debian 12
- How docker service was installed:
installed using docker compose. see compose file below

CPU architecture

x86-64

Docker creation

services:
  pairdrop:
    image: lscr.io/linuxserver/pairdrop:latest
    container_name: pairdrop
    environment:
      - PUID=1000
      - PGID=1000
      - TZ=Etc/UTC
      - RATE_LIMIT=false #optional
      - WS_FALLBACK=false #optional
      # - RTC_CONFIG= #optional
      - DEBUG_MODE=true #optional
    #ports:
    #  - 3000:3000
    labels:
      - "traefik.enable=true"
      - "traefik.http.routers.pairdrop.entrypoints=web"
      - "traefik.http.routers.pairdrop.rule=Host(`pairdrop.local.domain`)"
      - "traefik.http.middlewares.pairdrop-https-redirect.redirectscheme.scheme=websecure"
      - "traefik.http.routers.pairdrop.middlewares=pairdrop-https-redirect"
      - "traefik.http.routers.pairdrop-secure.entrypoints=websecure"
      - "traefik.http.routers.pairdrop-secure.rule=Host(`pairdrop.local.domain`)"
      - "traefik.http.routers.pairdrop-secure.tls=true"
      - "traefik.http.routers.pairdrop-secure.service=pairdrop"
      - "traefik.http.services.pairdrop.loadbalancer.server.port=3000"
    restart: unless-stopped
    networks:
      - proxy
networks:
  proxy:
    external: true

### Container logs

```bash
[migrations] started
[migrations] no migrations found
───────────────────────────────────────

      ██╗     ███████╗██╗ ██████╗
      ██║     ██╔════╝██║██╔═══██╗
      ██║     ███████╗██║██║   ██║
      ██║     ╚════██║██║██║   ██║
      ███████╗███████║██║╚██████╔╝
      ╚══════╝╚══════╝╚═╝ ╚═════╝

   Brought to you by linuxserver.io
───────────────────────────────────────

To support the app dev(s) visit:
PairDrop: https://www.buymeacoffee.com/pairdrop

To support LSIO projects visit:
https://www.linuxserver.io/donate/

───────────────────────────────────────
GID/UID
───────────────────────────────────────

User UID:    1000
User GID:    1000
───────────────────────────────────────
Linuxserver.io version: v1.10.8-ls77
Build-date: 2024-05-31T16:06:46+00:00
───────────────────────────────────────

[custom-init] No custom files found, skipping...

> pairdrop@1.10.8 start
> node server/index.js  

DEBUG_MODE is active. To protect privacy, do not use in production.

----DEBUG ENVIRONMENT VARIABLES----
{
    "debugMode": true,
    "port": 3000,
    "wsFallback": false,
    "rtcConfig": {
        "sdpSemantics": "unified-plan",
        "iceServers": [
            {
                "urls": "stun:stun.l.google.com:19302"
            }
        ]
    },
    "signalingServer": false,
    "ipv6Localize": false,
    "rateLimit": false,
    "buttons": {
        "donation_button": {},
        "twitter_button": {},
        "mastodon_button": {},
        "bluesky_button": {},
        "custom_button": {},
        "privacypolicy_button": {}
    },
    "autoStart": false,
    "localhostOnly": false
}

PairDrop is running on port 3000
[ls.io-init] done.

----DEBUGGING-PEER-IP-START----
remoteAddress: ::ffff:172.25.0.2
x-forwarded-for: 192.168.50.186
cf-connecting-ip: undefined
PairDrop uses: 192.168.50.186
IP is private: true
if IP is private, '127.0.0.1' is used instead
----DEBUGGING-PEER-IP-END----

----DEBUGGING-PEER-IP-START----
remoteAddress: ::ffff:172.25.0.2
x-forwarded-for: 192.168.50.124
cf-connecting-ip: undefined
PairDrop uses: 192.168.50.124
IP is private: true
if IP is private, '127.0.0.1' is used instead
----DEBUGGING-PEER-IP-END----

----DEBUGGING-PEER-IP-START----
remoteAddress: ::ffff:172.25.0.2
x-forwarded-for: 192.168.50.124
cf-connecting-ip: undefined
PairDrop uses: 192.168.50.124
IP is private: true
if IP is private, '127.0.0.1' is used instead
----DEBUGGING-PEER-IP-END----

----DEBUGGING-PEER-IP-START----
remoteAddress: ::ffff:172.25.0.2
x-forwarded-for: 192.168.50.186
cf-connecting-ip: undefined
PairDrop uses: 192.168.50.186
IP is private: true
if IP is private, '127.0.0.1' is used instead
----DEBUGGING-PEER-IP-END----

----DEBUGGING-PEER-IP-START----
remoteAddress: ::ffff:172.25.0.2
x-forwarded-for: 192.168.50.124
cf-connecting-ip: undefined
PairDrop uses: 192.168.50.124
IP is private: true
if IP is private, '127.0.0.1' is used instead
----DEBUGGING-PEER-IP-END----

----DEBUGGING-PEER-IP-START----
remoteAddress: ::ffff:172.25.0.2
x-forwarded-for: 192.168.50.186
cf-connecting-ip: undefined
PairDrop uses: 192.168.50.186
IP is private: true
if IP is private, '127.0.0.1' is used instead
----DEBUGGING-PEER-IP-END----

----DEBUGGING-PEER-IP-START----
remoteAddress: ::ffff:172.25.0.2
x-forwarded-for: 192.168.50.124
cf-connecting-ip: undefined
PairDrop uses: 192.168.50.124
IP is private: true
if IP is private, '127.0.0.1' is used instead
----DEBUGGING-PEER-IP-END----
github-actions[bot] commented 4 months ago

Thanks for opening your first issue here! Be sure to follow the relevant issue templates, or risk having this issue marked as invalid.

j0nnymoe commented 4 months ago

Have you tested without traefik in place first? (Access directly via IP)

back-lacking commented 4 months ago

@j0nnymoe i have not yet. I will try that when im able to.

back-lacking commented 4 months ago

Have you tested without traefik in place first? (Access directly via IP)

i have set my docker compose back to the default one on the read me and the issue still persists.

back-lacking commented 4 months ago

@j0nnymoe I havent gotten a response in a decent while.

j0nnymoe commented 4 months ago

Could you provide logs of when accessing directly via ip? I suspect this might be a problem:

IP is private: true
if IP is private, '127.0.0.1' is used instead

But also, I don't use pairdrop so need to see if anyone else that does can chime in.

Also, side note, I would say 3 days without a response isn't a "decent while".

back-lacking commented 4 months ago

Could you provide logs of when accessing directly via ip? I suspect this might be a problem:

IP is private: true
if IP is private, '127.0.0.1' is used instead

But also, I don't use pairdrop so need to see if anyone else that does can chime in.

Also, side note, I would say 3 days without a response isn't a "decent while".

i can provide a log, gimme a min

back-lacking commented 4 months ago 
[migrations] started
[migrations] no migrations found
───────────────────────────────────────

      ██╗     ███████╗██╗ ██████╗
      ██║     ██╔════╝██║██╔═══██╗
      ██║     ███████╗██║██║   ██║
      ██║     ╚════██║██║██║   ██║
      ███████╗███████║██║╚██████╔╝
      ╚══════╝╚══════╝╚═╝ ╚═════╝

   Brought to you by linuxserver.io
───────────────────────────────────────

To support the app dev(s) visit:
PairDrop: https://www.buymeacoffee.com/pairdrop

To support LSIO projects visit:
https://www.linuxserver.io/donate/

───────────────────────────────────────
GID/UID
───────────────────────────────────────

User UID:    1000
User GID:    1000
───────────────────────────────────────
Linuxserver.io version: v1.10.8-ls77
Build-date: 2024-05-31T16:06:46+00:00
───────────────────────────────────────

[custom-init] No custom files found, skipping...

> pairdrop@1.10.8 start
> node server/index.js

PairDrop is running on port 3000
[ls.io-init] done.

Just tried to pair the devices (phone and laptop), and put them in the same room. although on my phone, i was able to see the "device" (that was my phone) on the other tab.

j0nnymoe commented 4 months ago

No issues here locally, have spun up a quick test and able to see my phone over vlans image

back-lacking commented 4 months ago

@j0nnymoe weird. Both of my devices are on the same network

back-lacking commented 4 months ago

I have also not setup any vlans afaik

back-lacking commented 4 months ago

Well, i gotta go do some stuff so ill be gone for an hr. Sorry in advance.

j0nnymoe commented 4 months ago

The github issues are for bugs with the container where as this kind of support is more suited to our forum or discord. I would suggest coming over to either of those platforms to continue this. It feels like there is a wider issue on your network that could be stopping this considering you were able to see between 2 tabs on 1 device.

back-lacking commented 4 months ago

The github issues are for bugs with the container where as this kind of support is more suited to our forum or discord. I would suggest coming over to either of those platforms to continue this. It feels like there is a wider issue on your network that could be stopping this considering you were able to see between 2 tabs on 1 device.

i see. so i go to the linuxserver forums or discord for this?

j0nnymoe commented 4 months ago

Correct

back-lacking commented 4 months ago

man i need to verify with a number to get into the discord...

back-lacking commented 4 months ago

closing issue. issue is likely something outside of the docker image.