search

webrtc / apprtc

appr.tc has been shutdown. Please use the Dockerfile to run your own test/dev instance.
BSD 3-Clause "New" or "Revised" License
4.17k stars 1.37k forks source link

collider build failed #556

Open dandingol03 opened 6 years ago

dandingol03 commented 6 years ago

Browsers and versions affected browser:chrome

Description After I run go test collider,there is some log below:

collider
../../go/src/collider/dashboard_test.go:35: Errorf format %d has arg expected of wrong type string
../../go/src/collider/room_test.go:89: Errorf format %v reads arg #4, but call has only 3 args
FAIL    collider [build failed]

Steps to reproduce 1.go get collidermain 2.go install collidermain 3.generate ssh certificate 4.run go test collider

denniswon commented 6 years ago

Any update on this issue? Having the same prob.

Also, running the server also fails for me using tls: $GOPATH/bin/collidermain -port=8089 -tls=true

2018/05/20 09:48:35 Starting collider: tls = true, port = 8089, room-server=https://appr.tc 2018/05/20 09:48:35 Run: open /cert/cert.pem: no such file or directory

Could anyone please help? Thanks in advance.

deboc commented 6 years ago

Hi, same cast issue here with the Errorf.

@denniswon you probably forgot to create a certificate, like:

sudo mkdir -p /cert
sudo openssl req -x509 -newkey rsa:2048 -keyout /cert/key.pem -out /cert/cert.pem -days 99999 -nodes
swifticus2 commented 6 years ago

Did anyone resolve this?

ivdmitry commented 6 years ago

Hello I have the same error

~$ go test collider

collider

/src/collider/dashboard_test.go:35: Errorf format %d has arg expected of wrong type string /src/collider/room_test.go:89: Errorf format %v reads arg #4, but call has only 3 args

the certificate created collidermain starting work but on client webrtc WebSocket connection to 'wss://test.realmax.fi:8089/ws' failed: Error in connection establishment: net::ERR_CERT_AUTHORITY_INVALID

einsteinarbert commented 6 years ago

Hi, same cast issue here with the Errorf.

@denniswon you probably forgot to create a certificate, like:

sudo mkdir -p /cert
sudo openssl req -x509 -newkey rsa:2048 -keyout /cert/key.pem -out /cert/cert.pem -days 99999 -nodes

Thank you, I did it, just: sudo chmod -R a+r /cert/

EliosSs commented 5 years ago

Hi! excuse me, any update on this error? I am having the same issue.

I already created the certificates and when I run $go test collider

crashes with the message:

collider ../../../../../../Educational/go/src/collider/dashboard_test.go:35:3: Errorf format %d has arg expected of wrong type string ../../../../../../Educational/go/src/collider/room_test.go:89:3: Errorf format %v reads arg #4, but call has 3 args FAIL collider [build failed]

einsteinarbert commented 5 years ago

i didn't run this test

On Tue, Aug 13, 2019, 20:31 Eliomar Conde notifications@github.com wrote:

Hi! excuse me, any update on this error? I am having the same issue.

I already created the certificates and when I run $go test collider

crashes with the message:

collider ../../../../../../Educational/go/src/collider/dashboard_test.go:35:3: Errorf format %d has arg expected of wrong type string ../../../../../../Educational/go/src/collider/room_test.go:89:3: Errorf format %v reads arg #4 https://github.com/webrtc/apprtc/issues/4, but call has 3 args FAIL collider [build failed]

— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/webrtc/apprtc/issues/556?email_source=notifications&email_token=ACELXBAWOE5E4HCPD5BW773QEKZUVA5CNFSM4E6OA3MKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD4FVD5Q#issuecomment-520835574, or mute the thread https://github.com/notifications/unsubscribe-auth/ACELXBH2LPIWH5GFADJYWWTQEKZUVANCNFSM4E6OA3MA .

EliosSs commented 5 years ago

but you could use the collider program normally? I mean it is not mandatory for the operation of the program?

einsteinarbert commented 5 years ago

Yes, I just did following readme manual page of collinder. But you should attention about path of project, I build successfully on ubuntu >= 16.04, you should search this keyword [hieu19926, einsteinarbert, collinder] in google, here is my tree directory: [root@ctr486333 goWorkspace]# tree -L 3 /cert/cert.pem /cert/key.pem . ├── bin │ └── collidermain ├── collider.log ├── nohup.out ├── pkg │ └── linux_386 │ └── golang.org ├── src │ ├── collider -> /root/uav-project/apprtc/src/collider/src/collider │ ├── collidermain -> /root/uav-project/apprtc/src/collider/src/collidermain │ ├── collidertest -> /root/uav-project/apprtc/src/collider/src/collidertest │ ├── golang.org │ │ └── x │ └── nohup.out └── start.sh

in .bashrc:

export GOROOT=/root/uav-project/go export GOPATH=/root/uav-project/goWorkspace export GOBIN=$GOROOT/bin export PATH=$PATH:$GOBIN:$GOPATH

Vào Th 4, 14 thg 8, 2019 vào lúc 09:13 Eliomar Conde < notifications@github.com> đã viết:

but you could use the collider program normally? I mean it is not mandatory for the operation of the program?

— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/webrtc/apprtc/issues/556?email_source=notifications&email_token=ACELXBD5CMLAPBXKPB4UC4LQENS6NA5CNFSM4E6OA3MKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD4HPZHY#issuecomment-521075871, or mute the thread https://github.com/notifications/unsubscribe-auth/ACELXBEGQ4UEWAR7APKVES3QENS6NANCNFSM4E6OA3MA .

einsteinarbert commented 5 years ago

But now when I deploy apprtc on google cloud, I can connect via chrome of Android without any error but My android native app can't connect, collinder error shown: 2019/08/15 16:52:00 http: TLS handshake error from 117.6.160.102:18961: remote error: tls: unknown certificate I don't know why because in my server using dev test to run Apprtc, Andriod worked perfect. Difference is in my server, I used my cert file, but in google cloud I don't use any thing, the domain auto switch to https: https://my-project-id.appspot.com

einsteinarbert commented 4 years ago

cert.pem file is a full chain file (join public and private key into one text file cert.pem) :

SSL Collider: /cert/

Collider using full chain file: -----BEGIN CERTIFICATE----- (Your Primary SSL certificate: your_domain_name.crt) -----END CERTIFICATE----- -----BEGIN RSA PRIVATE KEY----- (Your Private Key: your_domain_name.key) -----END RSA PRIVATE KEY-----

SSL Apprtc: config command direct to /root/ssl/

Aprtc using full.pem file. Structure of full.pem (full chain cert file): -----BEGIN RSA PRIVATE KEY----- (Your Private Key: your_domain_name.key) -----END RSA PRIVATE KEY----- -----BEGIN CERTIFICATE----- (Your Primary SSL certificate: your_domain_name.crt) -----END CERTIFICATE----- -----BEGIN CERTIFICATE----- (Your Intermediate certificate: Chain_RootCA_Bundle.crt) -----END CERTIFICATE----- -----BEGIN CERTIFICATE----- (Your Root certificate: Chain_RootCA_Bundle.crt) -----END CERTIFICATE-----

SSL turnserver: config in /etc/turnserver.conf to /root/ssl/

einsteinarbert commented 4 years ago

Dont using google deploy, just using your VPS server, -- tobe continue update late....--

wcxdhr commented 4 years ago

But now when I deploy apprtc on google cloud, I can connect via chrome of Android without any error but My android native app can't connect, collinder error shown: 2019/08/15 16:52:00 http: TLS handshake error from 117.6.160.102:18961: remote error: tls: unknown certificate I don't know why because in my server using dev test to run Apprtc, Andriod worked perfect. Difference is in my server, I used my cert file, but in google cloud I don't use any thing, the domain auto switch to https: https://my-project-id.appspot.com

Same issue. I just used these commands to generate certificate. 

sudo mkdir -p /cert
sudo openssl req -x509 -newkey rsa:2048 -keyout /cert/key.pem -out /cert/cert.pem -days 99999 -nodes

Do you know how to solve this?

einsteinarbert commented 4 years ago

just buy a real cert for your server. In Android, we must to use real cert file.

Vào Th 4, 5 thg 8, 2020 vào lúc 13:21 wcxdhr notifications@github.com đã viết:

But now when I deploy apprtc on google cloud, I can connect via chrome of Android without any error but My android native app can't connect, collinder error shown: 2019/08/15 16:52:00 http: TLS handshake error from 117.6.160.102:18961: remote error: tls: unknown certificate I don't know why because in my server using dev test to run Apprtc, Andriod worked perfect. Difference is in my server, I used my cert file, but in google cloud I don't use any thing, the domain auto switch to https: https://my-project-id.appspot.com

Same issue. I just used these commands to generate certificate.

sudo mkdir -p /cert sudo openssl req -x509 -newkey rsa:2048 -keyout /cert/key.pem -out /cert/cert.pem -days 99999 -nodes

Do you know how to solve this?

— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/webrtc/apprtc/issues/556#issuecomment-669004545, or unsubscribe https://github.com/notifications/unsubscribe-auth/ACELXBGKB4B7KRC7QAHZFDDR7D26VANCNFSM4E6OA3MA .