Closed Iwhite67 closed 2 years ago
Hi!
Very odd you're using Ubuntu, but are you using an arm device like a raspberry Pi? I'm unsure as to why it's looking for an arm64/V8, which it's currently not supported for - as seen here https://github.com/PhlexPlexico/G5V/pkgs/container/g5v
I can try and get it compiled with that architecture, but I believe I was running into some problems previously.
Thanks!
yes, i make my test on freebox server i don't have my prod serv on actualy :p
That may be why then! That being said, I think the API may have troubles compiling since bcrypt has to be compiled during build... Maybe I'll try adding it, but I can't guarantee it'll work on that arch!
i can try on my prod server but i have one question, is a problem to have caddy on same server of nginx ?
i have a server with nginx / mariadb / pterodactyl.
It shouldn't be an issue! All you have to change in the docker compose is the port and forward requests from NGINX -> Caddy. So in the docker-compose just change the ports under the caddy
service to something like this -
ports:
- "9000:80"
And on your NGINX you have to find what the IP address and do the forwarding with the reverse proxy and whatnot - so you can probably convert this Caddy setup to Nginx:
get5.phlexplexi.co {
reverse_proxy 172.18.0.5
request_body {
max_size 256MB
}
route /api/* {
uri strip_prefix /api
reverse_proxy http://172.18.0.4:3301
}
}
Where the 172... addresses are from Docker, using something like the following -
docker container inspect G5API | grep -i IPAddress
docker container inspect G5V-Front-End | grep -i IPAddress
If mariadb is using the default SQL port, you'll just have to adjust that in your docker-compose as well :)
TL;DR just setup Nginx as your reverse proxy and adjust ports as necessary!
E: If you wait though, I'll see if I can get that arm build up and running as well.
Thanks you, i check this weekend.
Another thing, in your docker-compose for G5V and G5API, would you mind trying to add platform: linux/amd64
? For example:
g5v:
image: ghcr.io/phlexplexico/g5v:latest
depends_on:
- g5api
- caddy
container_name: G5V-Front-End
restart: always
platform: linux/amd64
networks:
- get5
and then try running it? See what happens?
Thanks!
I try after eat and I you say
Alexis Zaun Technicien SAV Nord Est
FOM Industrie FRANCE
@.**@.> (+33) 06 40 62 82 45
From: PhlexPlexico @.> Sent: Tuesday, April 26, 2022 7:14:24 PM To: PhlexPlexico/G5V @.> Cc: Iwhite67 @.>; Author @.> Subject: Re: [PhlexPlexico/G5V] No matching Manifest Docker Compose (Issue #131)
Another thing, in your docker-compose for G5V and G5API, would you mind trying to add platform: linux/amd64? For example:
g5v: image: ghcr.io/phlexplexico/g5v:latest depends_on:
and then try running it? See what happens?
Thanks!
— Reply to this email directly, view it on GitHubhttps://github.com/PhlexPlexico/G5V/issues/131#issuecomment-1110050500, or unsubscribehttps://github.com/notifications/unsubscribe-auth/ACJ75FCHGHHNQ43UTYSJIQLVHAP7BANCNFSM5UMOR4GQ. You are receiving this because you authored the thread.Message ID: @.***>
ERROR: The Compose file './docker-compose.yml' is invalid because: Unsupported config option for services.g5v: 'platform'
Hmm you may have to bump the version
at the top to 3
instead of 2
... Very odd, I guess it may not be able to build due to nginx not having that build file either. Very odd, indeed!
Thanks!
Starting get5db ... done
Recreating caddy-reverse-proxy ... error
Starting G5API ...
ERROR: for caddy-reverse-proxy Cannot start service caddy: OCI runtime create failed: container_linux.go:380: starting container process caused: process_linux.go:545: container init caused: rootfs_linux.go:76: mounting "/root/get5/Caddyfile" to rootfs at "/etc/caddy/Caddyfile" caused: mount through procfd: not a directory: unknown: Are you trying to mount a direcStarting G5API ... done
version: '2.1'
networks:
get5:
external: true
services:
caddy:
image: caddy:2-alpine
container_name: caddy-reverse-proxy
restart: unless-stopped
ports:
- "8080:80"
volumes:
- ./Caddyfile:/etc/caddy/Caddyfile
networks:
- get5
environment:
- CADDY_URL=http://match.cs.white-gaming.fr
- CADDY_API_ENDPOINT=api
- CADDY_REVERSE_PROXY_PORT=3301
get5db:
image: yobasystems/alpine-mariadb
container_name: get5db
restart: always
environment:
- MYSQL_ROOT_PASSWORD=
- MYSQL_DATABASE=get5
- MYSQL_USER=get5
- MYSQL_PASSWORD=
ports:
- "3307:3306"
networks:
- get5
g5api:
image: ghcr.io/phlexplexico/g5api:latest
depends_on:
- get5db
container_name: G5API
volumes:
- redisVol:/RedisFiles
expose:
- 3301
environment:
- PORT=3301
- HOSTNAME=http://match.cs.white-gaming.fr
- DBKEY=
- STEAMAPIKEY=
- SHAREDSECRET=funzilat
- CLIENTHOME=http://match.cs.white-gaming.fr
- APIURL=http://match.cs.white-gaming.fr/api
- SQLUSER=get5
- SQLPASSWORD=
- SQLPORT=3306
- DATABASE=get5
- SQLHOST=get5db
- ADMINS=
- SUPERADMINS=76561198033164185
- REDISPASSWORD=
- UPLOADDEMOS=true
restart: unless-stopped
networks:
- get5
g5v:
image: ghcr.io/phlexplexico/g5v:latest
depends_on:
- g5api
- caddy
container_name: G5V-Front-End
restart: always
networks:
- get5
volumes:
redisVol:
external: false
fix
so, i have website but problem with API
when i click on sign in
# Port listen
listen 80;
# DNS Record for catch request
server_name match.cs.white-gaming.fr;
# Open block for process forward request
location /{
# Server where traffic is transferred
proxy_pass http://172.18.0.4;
# Include file proxy_params with general param
include proxy_params;
}
location /api/* {
proxy_pass http://172.18.0.5:3301;
include proxy_params;
}
}
./Caddyfile:/etc/caddy/Caddyfile to
- ./Caddyfile:/etc/caddy/Caddyfile.conf
fix
This should do nothing. As you can see in the repo, there is a file named Caddyfile
, please make sure your images are up to date. The Caddyfile is a no extension file and will fail to read on that reverse proxy if you use it like that I think.
https://github.com/PhlexPlexico/G5API/blob/master/Caddyfile
Starting get5db ... done Recreating caddy-reverse-proxy ... error Starting G5API ... ERROR: for caddy-reverse-proxy Cannot start service caddy: OCI runtime create failed: container_linux.go:380: starting container process caused: process_linux.go:545: container init caused: rootfs_linux.go:76: mounting "/root/get5/Caddyfile" to rootfs at "/etc/caddy/Caddyfile" caused: mount through procfd: not a directory: unknown: Are you trying to mount a direcStarting G5API ... done
version: '2.1' networks: get5: external: true services: caddy: image: caddy:2-alpine container_name: caddy-reverse-proxy restart: unless-stopped ports: - "8080:80" volumes: - ./Caddyfile:/etc/caddy/Caddyfile networks: - get5 environment: - CADDY_URL=http://match.cs.white-gaming.fr - CADDY_API_ENDPOINT=api - CADDY_REVERSE_PROXY_PORT=3301 get5db: image: yobasystems/alpine-mariadb container_name: get5db restart: always environment: - MYSQL_ROOT_PASSWORD= - MYSQL_DATABASE=get5 - MYSQL_USER=get5 - MYSQL_PASSWORD= ports: - "3307:3306" networks: - get5 g5api: image: ghcr.io/phlexplexico/g5api:latest depends_on: - get5db container_name: G5API volumes: - redisVol:/RedisFiles expose: - 3301 environment: - PORT=3301 - HOSTNAME=http://match.cs.white-gaming.fr - DBKEY= - STEAMAPIKEY= - SHAREDSECRET=funzilat - CLIENTHOME=http://match.cs.white-gaming.fr - APIURL=http://match.cs.white-gaming.fr/api - SQLUSER=get5 - SQLPASSWORD= - SQLPORT=3306 - DATABASE=get5 - SQLHOST=get5db - ADMINS= - SUPERADMINS=76561198033164185 - REDISPASSWORD= - UPLOADDEMOS=true restart: unless-stopped networks: - get5 g5v: image: ghcr.io/phlexplexico/g5v:latest depends_on: - g5api - caddy container_name: G5V-Front-End restart: always networks: - get5 volumes: redisVol: external: false
As for this, the database is on the wrong port. You changed the port of the database instance so this needs to change as well - SQLPORT=3306
.
so, i have website but problem with API
when i click on sign in
# Port listen listen 80; # DNS Record for catch request server_name match.cs.white-gaming.fr; # Open block for process forward request location /{ # Server where traffic is transferred proxy_pass http://172.18.0.4; # Include file proxy_params with general param include proxy_params; } location /api/* { proxy_pass http://172.18.0.5:3301; include proxy_params; } }
Per the wiki - the location for the API block should be as follows:
location /api/ {
proxy_pass http://172.18.0.5:3301;
proxy_http_version 1.1;
proxy_set_header Upgrade $http_upgrade;
proxy_set_header Connection 'upgrade';
proxy_set_header Host $host;
proxy_cache_bypass $http_upgrade;
}
I think the same should be done for the front-end as well.
location / {
proxy_pass http://172.18.0.4;
proxy_http_version 1.1;
proxy_set_header Upgrade $http_upgrade;
proxy_set_header Connection 'upgrade';
proxy_set_header Host $host;
proxy_cache_bypass $http_upgrade;
}
Since you're not using the reverse proxy, you can remove that caddy image entirely and it shouldn't cause any issues.
./Caddyfile:/etc/caddy/Caddyfile to
- ./Caddyfile:/etc/caddy/Caddyfile.conf
fix
This should do nothing. As you can see in the repo, there is a file named
Caddyfile
, please make sure your images are up to date. The Caddyfile is a no extension file and will fail to read on that reverse proxy if you use it like that I think. https://github.com/PhlexPlexico/G5API/blob/master/Caddyfile
strange, i running on last image
Starting get5db ... done Recreating caddy-reverse-proxy ... error Starting G5API ... ERROR: for caddy-reverse-proxy Cannot start service caddy: OCI runtime create failed: container_linux.go:380: starting container process caused: process_linux.go:545: container init caused: rootfs_linux.go:76: mounting "/root/get5/Caddyfile" to rootfs at "/etc/caddy/Caddyfile" caused: mount through procfd: not a directory: unknown: Are you trying to mount a direcStarting G5API ... done
As for this, the database is on the wrong port. You changed the port of the database instance so this needs to change as well
- SQLPORT=3306
.
i have allready a mariadb who running on 3306, i change the port of get5db to 3307:3306
Per the wiki - the location for the API block should be as follows:
location /api/ { proxy_pass http://172.18.0.5:3301; proxy_http_version 1.1; proxy_set_header Upgrade $http_upgrade; proxy_set_header Connection 'upgrade'; proxy_set_header Host $host; proxy_cache_bypass $http_upgrade; }
I think the same should be done for the front-end as well.
location / { proxy_pass http://172.18.0.4; proxy_http_version 1.1; proxy_set_header Upgrade $http_upgrade; proxy_set_header Connection 'upgrade'; proxy_set_header Host $host; proxy_cache_bypass $http_upgrade; }
Since you're not using the reverse proxy, you can remove that caddy image entirely and it shouldn't cause any issues.
if i remove caddy, i lost the access, but if i keep caddy, i have access
Well, Caddy is effectively doing nothing if you have your NGINX doing all the proxy requests for you. Did you remove the depends in the g5v part of the docker file?
g5v:
image: ghcr.io/phlexplexico/g5v:latest
depends_on:
- g5api
- caddy
Remove caddy from there and try building again, it should run without issue. then grab the IP addresses once more from the containers and update them in your nginx conf.
Well, Caddy is effectively doing nothing if you have your NGINX doing all the proxy requests for you. Did you remove the depends in the g5v part of the docker file?
g5v: image: ghcr.io/phlexplexico/g5v:latest depends_on: - g5api - caddy
Remove caddy from there and try building again, it should run without issue. then grab the IP addresses once more from the containers and update them in your nginx conf.
Same, i have access, but nothing when i click on sign in
i thinks for me, Vue can't communicating with API
Sorry, i'm very noob on this side, i'm best on SRCDS xD
Vue isn't communicating because it can't find the reverse call for /api/
. This either has to be done on nginx, or with the given Caddy reverse proxy, not both.
location /api/ {
proxy_pass http://172.18.0.5:3301;
proxy_http_version 1.1;
proxy_set_header Upgrade $http_upgrade;
proxy_set_header Connection 'upgrade';
proxy_set_header Host $host;
proxy_cache_bypass $http_upgrade;
}
This block in your NGINX conf will have https://match.cs.white-gaming.fr/api
-> http://172.18.0.5:3301
which is your internal Docker IP and port that you assigned it. Make sure your API is running as well and nothing has caused it to crash - docker container ls
and see if it's running.
Vue isn't communicating because it can't find the reverse call for
/api/
. This either has to be done on nginx, or with the given Caddy reverse proxy, not both.location /api/ { proxy_pass http://172.18.0.5:3301; proxy_http_version 1.1; proxy_set_header Upgrade $http_upgrade; proxy_set_header Connection 'upgrade'; proxy_set_header Host $host; proxy_cache_bypass $http_upgrade; }
This block in your NGINX conf will have
https://match.cs.white-gaming.fr/api
->http://172.18.0.5:3301
which is your internal Docker IP and port that you assigned it. Make sure your API is running as well and nothing has caused it to crash -docker container ls
and see if it's running.
G5API running
server{
# Port listen
listen 80;
# DNS Record for catch request
server_name match.cs.white-gaming.fr;
# Open block for process forward request
location / {
proxy_pass http://172.18.0.4;
proxy_http_version 1.1;
proxy_set_header Upgrade $http_upgrade;
proxy_set_header Connection 'upgrade';
proxy_set_header Host $host;
proxy_cache_bypass $http_upgrade;
}
location /api/ {
proxy_pass http://172.18.0.5:3301;
proxy_http_version 1.1;
proxy_set_header Upgrade $http_upgrade;
proxy_set_header Connection 'upgrade';
proxy_set_header Host $host;
proxy_cache_bypass $http_upgrade;
}
}
server{
# Port listen
listen 80;
# DNS Record for catch request
server_name match.cs.white-gaming.fr;
# Open block for process forward request
location / {
proxy_pass http://172.18.0.4;
proxy_http_version 1.1;
proxy_set_header Upgrade $http_upgrade;
proxy_set_header Connection 'upgrade';
proxy_set_header Host $host;
proxy_cache_bypass $http_upgrade;
}
}
location /api/ {
proxy_pass http://172.18.0.5:3301;
proxy_http_version 1.1;
proxy_set_header Upgrade $http_upgrade;
proxy_set_header Connection 'upgrade';
proxy_set_header Host $host;
proxy_cache_bypass $http_upgrade;
}
The location /api/ cannot be inside the root location.
ah, new step
GNU nano 4.8 /etc/nginx/sites-available/test.conf
server{
# Port listen
listen 80;
# DNS Record for catch request
server_name match.cs.white-gaming.fr;
# Open block for process forward request
location / {
proxy_pass http://172.18.0.4;
proxy_http_version 1.1;
proxy_set_header Upgrade $http_upgrade;
proxy_set_header Connection 'upgrade';
proxy_set_header Host $host;
proxy_cache_bypass $http_upgrade;
location /api/ {
proxy_pass http://172.18.0.3:3301;
proxy_http_version 1.1;
proxy_set_header Upgrade $http_upgrade;
proxy_set_header Connection 'upgrade';
proxy_set_header Host $host;
proxy_cache_bypass $http_upgrade;
}
}
}
wrong ip set, i set root to vue ip api to api ip
Once again, please move location /api/
outside of the location /
block.
server{
# Port listen
listen 80;
# DNS Record for catch request
server_name match.cs.white-gaming.fr;
# Open block for process forward request
location / {
proxy_pass http://172.18.0.4;
proxy_http_version 1.1;
proxy_set_header Upgrade $http_upgrade;
proxy_set_header Connection 'upgrade';
proxy_set_header Host $host;
proxy_cache_bypass $http_upgrade;
}
location /api/ {
proxy_pass http://172.18.0.3:3301;
proxy_http_version 1.1;
proxy_set_header Upgrade $http_upgrade;
proxy_set_header Connection 'upgrade';
proxy_set_header Host $host;
proxy_cache_bypass $http_upgrade;
}
}
sorry, i have not understand
Once again, please move
location /api/
outside of thelocation /
block.server{ # Port listen listen 80; # DNS Record for catch request server_name match.cs.white-gaming.fr; # Open block for process forward request location / { proxy_pass http://172.18.0.4; proxy_http_version 1.1; proxy_set_header Upgrade $http_upgrade; proxy_set_header Connection 'upgrade'; proxy_set_header Host $host; proxy_cache_bypass $http_upgrade; } location /api/ { proxy_pass http://172.18.0.3:3301; proxy_http_version 1.1; proxy_set_header Upgrade $http_upgrade; proxy_set_header Connection 'upgrade'; proxy_set_header Host $host; proxy_cache_bypass $http_upgrade; } }
hum, my initial nginx config have same format of your last
initial
your last version
my actual init
ah, new step
GNU nano 4.8 /etc/nginx/sites-available/test.conf server{ # Port listen listen 80; # DNS Record for catch request server_name match.cs.white-gaming.fr; # Open block for process forward request location / { proxy_pass http://172.18.0.4; proxy_http_version 1.1; proxy_set_header Upgrade $http_upgrade; proxy_set_header Connection 'upgrade'; proxy_set_header Host $host; proxy_cache_bypass $http_upgrade; location /api/ { proxy_pass http://172.18.0.3:3301; proxy_http_version 1.1; proxy_set_header Upgrade $http_upgrade; proxy_set_header Connection 'upgrade'; proxy_set_header Host $host; proxy_cache_bypass $http_upgrade; } } }
wrong ip set, i set root to vue ip api to api ip
This last comment shows it was not closed prior to.
If you navigate to match.cs.white-gaming.fr/api
does it redirect anywhere?
actualy, i have loading please wait into all page, and when i click on sign in, i have error : not found
Oh this is because it's not removing the api
from the call... in the location /api/
your proxy_pass needs a slash at the end!
proxy_pass http://172.18.0.3:3301/;
ok, this is good
i have steam login page, after connect, he come back to home but not connected
and pages have again loading
I LOVE !! xD
soon the end
Okay well that's a positive! It means the API is interacting properly!! So next up, this may be a bug bit I'm just confirming with a fresh database instance. Are you able to go create teams and whatnot?
Okay well that's a positive! It means the API is interacting properly!! So next up, this may be a bug bit I'm just confirming with a fresh database instance. Are you able to go create teams and whatnot?
no because he don't connect after steam
get5db:
image: yobasystems/alpine-mariadb
container_name: get5db
restart: always
environment:
- MYSQL_ROOT_PASSWORD=
- MYSQL_DATABASE=get5
- MYSQL_USER=get5
- MYSQL_PASSWORD=
ports:
- "3307:3306"
networks:
- get5
g5api:
image: ghcr.io/phlexplexico/g5api:latest
depends_on:
- get5db
container_name: G5API
volumes:
- redisVol:/RedisFiles
expose:
- 3301
environment:
- PORT=3301
- HOSTNAME=http://match.cs.white-gaming.fr
- DBKEY=
- STEAMAPIKEY=
- SHAREDSECRET=
- CLIENTHOME=http://match.cs.white-gaming.fr
- APIURL=http://match.cs.white-gaming.fr/api/
- SQLUSER=get5
- SQLPASSWORD=
- SQLPORT=3306
- DATABASE=get5
- SQLHOST=get5db
- ADMINS=
- SUPERADMINS=76561198033164185
- REDISPASSWORD=
- UPLOADDEMOS=true
restart: unless-stopped
networks:
on this server, i have mariadb on 3306
So you already have a SQL database? You're going to need to change the following, or just use it's own database instance (probably easier?)
environment:
- PORT=3301
- HOSTNAME=http://match.cs.white-gaming.fr
- DBKEY=
- STEAMAPIKEY=
- SHAREDSECRET=
- CLIENTHOME=http://match.cs.white-gaming.fr
- APIURL=http://match.cs.white-gaming.fr/api/
- SQLUSER=get5 # MAKE SURE THIS USER EXISTS
- SQLPASSWORD= # I NEED A PASSWORD
- SQLPORT=3306
- DATABASE=get5 # MAKE SURE THIS DATABASE EXISTS
- SQLHOST=get5db # THIS HAS TO BE host.docker.internal
- ADMINS=
- SUPERADMINS=76561198033164185
- REDISPASSWORD=
- UPLOADDEMOS=true
Alternatively, if you wish to use the database that's in the compose file. just change - SQLPORT=3306
to - SQLPORT=3307
!
i check because i have user get5 but in localhost, i will go change
THIS HAS TO BE host.docker.internal
what is ?
host.docker.internal
redirects back to your host machine. I know you mentioned you are already running a MySQL database, which I assume is on the host machine and not another docker container, right? So we need to connect to that database. The host get5db
will resolve to whatever Docker IP the container get5db
is running. If you use localhost
on the image, it will look at 172.18.0.3
your container IP, not your host machine.
G5API | [1/6] Validating package.json...
G5API | [2/6] Resolving packages...
G5API | success Already up-to-date.
G5API | Done in 0.85s.
G5API | yarn run v1.22.18
G5API | $ MYSQL_FLAGS="-CONNECT_WITH_DB" db-migrate --env production --config config/production.json db:create get5
G5API | Ignoring invalid configuration option passed to Connection: driver. This is currently a warning, but in future versions of MySQL2, an error will be thrown if you pass an invalid configuration option to a Connection
G5API | Ignoring invalid configuration option passed to Connection: redisHost. This is currently a warning, but in future versions of MySQL2, an error will be thrown if you pass an invalid configuration option to a Connection
G5API | Ignoring invalid configuration option passed to Connection: redisPort. This is currently a warning, but in future versions of MySQL2, an error will be thrown if you pass an invalid configuration option to a Connection
G5API | Ignoring invalid configuration option passed to Connection: redisTTL. This is currently a warning, but in future versions of MySQL2, an error will be thrown if you pass an invalid configuration option to a Connection
G5API | Ignoring invalid configuration option passed to Connection: redisPass. This is currently a warning, but in future versions of MySQL2, an error will be thrown if you pass an invalid configuration option to a Connection
G5API | [ERROR] AssertionError [ERR_ASSERTION]: ifError got unwanted exception: getaddrinfo ENOTFOUND host.docker.internal
G5API | at /Get5API/G5API/node_modules/db-migrate/lib/commands/db.js:17:12
G5API | at /Get5API/G5API/node_modules/db-migrate/lib/driver/index.js:95:9
G5API | at /Get5API/G5API/node_modules/db-migrate-mysql/index.js:518:14
G5API | at Connection.<anonymous> (/Get5API/G5API/node_modules/mysql2/lib/connection.js:775:13)
G5API | at Object.onceWrapper (node:events:514:26)
G5API | at Connection.emit (node:events:394:28)
G5API | at Connection._notifyError (/Get5API/G5API/node_modules/mysql2/lib/connection.js:236:12)
G5API | at Connection._handleFatalError (/Get5API/G5API/node_modules/mysql2/lib/connection.js:167:10)
G5API | at Connection._handleNetworkError (/Get5API/G5API/node_modules/mysql2/lib/connection.js:180:10)
G5API | at Socket.emit (node:events:394:28)
G5API | at emitErrorNT (node:internal/streams/destroy:157:8)
G5API | at emitErrorCloseNT (node:internal/streams/destroy:122:3)
G5API | at processTicksAndRejections (node:internal/process/task_queues:83:21)
G5API | at GetAddrInfoReqWrap.onlookup [as oncomplete] (node:dns:71:26)
G5API | error Command failed with exit code 1.
G5API | info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.
G5API exited with code 1
getaddrinfo ENOTFOUND host.docker.internal
with 192.168.1.248 is good
Oh, well if it works with the IP then that's even better! So it's working now?
Oh, well if it works with the IP then that's even better! So it's working now?
No haha
G5API start but after connection, i'm not connected, match team etc have again loading
Okay, well it still launches and you were able to get to the database right? As you show, it did get inserted. Is there any logs on the API by any chance that are showing any GETs? docker container logs G5API
and try and load the main page :)
G5API | 0|G5API | GET /auth/steam 302 224.754 ms - 0
G5API | 0|G5API | ::ffff:172.18.0.1 - - [29/Apr/2022:15:29:41 +0000] "GET /auth/steam HTTP/1.1" 302 0 "http://match.cs.white-gaming.fr/" "Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/99.0.4844.84 Safari/537.36 OPR/85.0.4341.72"
G5API | 0|G5API | GET /auth/steam/return?openid.ns=http%3A%2F%2Fspecs.openid.net%2Fauth%2F2.0&openid.mode=id_res&openid.op_endpoint=https%3A%2F%2Fsteamcommunity.com%2Fopenid%2Flogin&openid.claimed_id=https%3A%2F%2Fsteamcommunity.com%2Fopenid%2Fid%2F76561198033164185&openid.identity=https%3A%2F%2Fsteamcommunity.com%2Fopenid%2Fid%2F76561198033164185&openid.return_to=http%3A%2F%2Fmatch.cs.white-gaming.fr%2Fapi%2F%2Fauth%2Fsteam%2Freturn&openid.response_nonce=2022-04-29T15%3A29%3A43ZWN06Lcyvkide2i8cgAJUlMH3%2FLs%3D&openid.assoc_handle=1234567890&openid.signed=signed%2Cop_endpoint%2Cclaimed_id%2Cidentity%2Creturn_to%2Cresponse_nonce%2Cassoc_handle&openid.sig=jBG3LlQ6ncwrDyV203HNa0OwmGQ%3D 302 769.463 ms - 106
G5API | 0|G5API | ::ffff:172.18.0.1 - - [29/Apr/2022:15:29:43 +0000] "GET /auth/steam/return?openid.ns=http%3A%2F%2Fspecs.openid.net%2Fauth%2F2.0&openid.mode=id_res&openid.op_endpoint=https%3A%2F%2Fsteamcommunity.com%2Fopenid%2Flogin&openid.claimed_id=https%3A%2F%2Fsteamcommunity.com%2Fopenid%2Fid%2F76561198033164185&openid.identity=https%3A%2F%2Fsteamcommunity.com%2Fopenid%2Fid%2F76561198033164185&openid.return_to=http%3A%2F%2Fmatch.cs.white-gaming.fr%2Fapi%2F%2Fauth%2Fsteam%2Freturn&openid.response_nonce=2022-04-29T15%3A29%3A43ZWN06Lcyvkide2i8cgAJUlMH3%2FLs%3D&openid.assoc_handle=1234567890&openid.signed=signed%2Cop_endpoint%2Cclaimed_id%2Cidentity%2Creturn_to%2Cresponse_nonce%2Cassoc_handle&openid.sig=jBG3LlQ6ncwrDyV203HNa0OwmGQ%3D HTTP/1.1" 302 106 "-" "Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/99.0.4844.84 Safari/537.36 OPR/85.0.4341.72"
G5V-Front-End | 172.18.0.1 - - [29/Apr/2022:15:29:43 +0000] "GET / HTTP/1.1" 304 0 "-" "Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/99.0.4844.84 Safari/537.36 OPR/85.0.4341.72" "-"
i have a get when i'm make the steam connection, but nothing if i go to all teams
Okay but what if you go to http://match.cs.white-gaming.fr/matches
what does it give you?
same of teams, no G5API request and loading please wait
It should have a log still when trying to request it... Oh actually that may be a try_files issue... Can you open your web console and check the network tab? And in your NGINX conf under location /
can you add the line try_files $uri /index.html;
?
DevTools failed to load source map: Could not parse content for http://match.cs.white-gaming.fr/js/277.ae7d1617.js.map: Unexpected token < in JSON at position 0
Hmm that's fine, could you try navigating to http://match.cs.white-gaming.fr/api/teams
or something similar? When you logged in, did it store your username in the database?
no username
i put Iwhite in username, Teams is loading now
Okay so if the /api/ call still isn't working, can you paste in your NGINX config again if you don't mind?
It should be something like
Thanks!
Okay so if the /api/ call still isn't working, can you paste in your NGINX config again if you don't mind?
It should be something like
Thanks!
with iwhite into username, is good
but before, username are empty
Hello, i use your docker-compose.yml and when i make docker-compose up, i have this error
i'm on Ubuntu 20.04
Pulling g5api (ghcr.io/phlexplexico/g5api:latest)... latest: Pulling from phlexplexico/g5api ERROR: no matching manifest for linux/arm64/v8 in the manifest list entries