[GH-ISSUE #489] proxy settings not handled from config.php #104

New issue

Open

opened 2026-02-26 05:33:13 +03:00 by kerem · 1 comment

kerem commented

2026-02-26 05:33:13 +03:00

Owner

Originally created by @eap1978 on GitHub (Mar 24, 2022).
Original GitHub issue: https://github.com/nextcloud/twofactor_gateway/issues/489

Hi,
i have NC server with proxy settings in config.php
...
'proxy' => 'proxy.server:3128',
...

but this setting do not handled by twofactor_gateway and it trying to send request to api.telegram directly.

TelegramBot\Api\HttpException: Failed to connect to api.telegram.org port 443: Connection refused

Originally created by @eap1978 on GitHub (Mar 24, 2022). Original GitHub issue: https://github.com/nextcloud/twofactor_gateway/issues/489 Hi, i have NC server with proxy settings in config.php ... 'proxy' => 'proxy.server:3128', ... but this setting do not handled by twofactor_gateway and it trying to send request to api.telegram directly. TelegramBot\Api\HttpException: Failed to connect to api.telegram.org port 443: Connection refused

kerem commented

2026-02-26 05:33:14 +03:00

Author

Owner

@vitormattos commented on GitHub (Apr 7, 2022):

Do you have all the backtrace of this error?

@vitormattos commented on GitHub (Apr 7, 2022): Do you have all the backtrace of this error?

kerem referenced this issue

2026-02-26 05:33:59 +03:00

[PR #104] [MERGED] Add basic setup instructions for the user settings #209

No milestone

No project

No assignees

1 participant

Notifications

Due date

The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference

starred/twofactor_gateway-nextcloud#104

No description provided.

Rows
Columns