-
Notifications
You must be signed in to change notification settings - Fork 450
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Remove dead links, unmaintained projects #1
Labels
Milestone
Comments
1 task
nodiscc
added a commit
that referenced
this issue
Aug 7, 2023
nodiscc
added a commit
that referenced
this issue
Aug 7, 2023
This was referenced Aug 22, 2023
This was referenced Aug 24, 2023
Merged
nodiscc
added a commit
that referenced
this issue
Aug 25, 2023
- No commits since 25 Nov 2022 https://codeberg.org/GNUsocial/gnu-social/commits/branch/v3 - ref. #1
nodiscc
added a commit
to sanch03/awesome-selfhosted-data
that referenced
this issue
Aug 25, 2023
- No commits since 25 Nov 2022 https://codeberg.org/GNUsocial/gnu-social/commits/branch/v3 - ref. awesome-selfhosted#1
Closed
nodiscc
added a commit
that referenced
this issue
Aug 27, 2023
- Ref. #1 - `ERROR:url_check.py: [528/1387] https://kolab.org/ : HTTPSConnectionPool(host='kolab.org', port=443): Max retries exceeded with url: / (Caused by ConnectTimeoutError(<urllib3.connection.HTTPSConnection object at 0x7f82d526be20>, 'Connection to kolab.org timed out. (connect timeout=10)'))` - `ERROR:url_check.py: [528/1387] https://git.kolab.org/ : HTTP 503`
nodiscc
added a commit
that referenced
this issue
Aug 27, 2023
- ref. #1 - `https://transfer.sh : HTTPSConnectionPool(host='transfer.sh', port=443): Max retries exceeded with url: / (Caused by NameResolutionError("<urllib3.connection.HTTPSConnection object at 0x7f82d5269180>: Failed to resolve 'transfer.sh' ([Errno -2] Name or service not known)"))` - ref. dutchcoders/transfer.sh#575
nodiscc
added a commit
that referenced
this issue
Aug 27, 2023
- ref. #1 - `https://wikisuite.org/Source-Code : HTTPSConnectionPool(host='wikisuite.org', port=443): Max retries exceeded with url: /Source-Code (Caused by ConnectTimeoutError(<urllib3.connection.HTTPSConnection object at 0x7f82d5269120>, 'Connection to wikisuite.org timed out. (connect timeout=10)'))` - `https://wikisuite.org : HTTPSConnectionPool(host='wikisuite.org', port=443): Max retries exceeded with url: / (Caused by ConnectTimeoutError(<urllib3.connection.HTTPSConnection object at 0x7f82d50d6a10>, 'Connection to wikisuite.org timed out. (connect timeout=10)'))`
nodiscc
pushed a commit
that referenced
this issue
Mar 6, 2025
- ref: #1 - `https://demo.mathesar.org/ : HTTPSConnectionPool(host='demo.mathesar.org', port=443): Max retries exceeded with url: / (Caused by ConnectTimeoutError(<urllib3.connection.HTTPSConnection object at 0x7facaf9a1700>, 'Connection to demo.mathesar.org timed out. (connect timeout=10)'))` - Demo seems to be removed, no mentions of it on website or repo
nodiscc
pushed a commit
that referenced
this issue
Mar 6, 2025
- ref: #1 - `https://www.linphone.org/technical-corner/flexisip/ : HTTP 404`
nodiscc
pushed a commit
that referenced
this issue
Mar 7, 2025
- ref: #1 - `https://openstreamingplatform.com : HTTPSConnectionPool(host='openstreamingplatform.com', port=443): Max retries exceeded with url: / (Caused by NameResolutionError("<urllib3.connection.HTTPSConnection object at 0x7facb29f63c0>: Failed to resolve 'openstreamingplatform.com' ([Errno -2] Name or service not known)"))` - https://gitlab.com/osp-group/flask-nginx-rtmp-manager : archived
nodiscc
pushed a commit
that referenced
this issue
Mar 7, 2025
- ref: #1 - `https://l33t.codes/xibalba-bbs/ : HTTPSConnectionPool(host='l33t.codes', port=443): Max retries exceeded with url: /xibalba-bbs/ (Caused by NewConnectionError('<urllib3.connection.HTTPSConnection object at 0x7facaf96e2d0>: Failed to establish a new connection: [Errno 111] Connection refused'))` - Neither website nor repo point to any demo
nodiscc
pushed a commit
that referenced
this issue
Mar 7, 2025
- ref: #1 - `https://demo.wikidocs.it : HTTPSConnectionPool(host='demo.wikidocs.it', port=443): Max retries exceeded with url: / (Caused by SSLError(SSLCertVerificationError(1, '[SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed: certificate has expired (_ssl.c:1000)')))` - SSL Error exists now for at least one month (https://github.com/awesome-selfhosted/awesome-selfhosted-data/actions/runs/13230224825/job/36926286512)
nodiscc
pushed a commit
that referenced
this issue
Mar 7, 2025
- ref: #1 - `https://www.pimcore.org/ : HTTPSConnectionPool(host='www.pimcore.org', port=443): Max retries exceeded with url: / (Caused by NameResolutionError("<urllib3.connection.HTTPSConnection object at 0x7facaf9a02f0>: Failed to resolve 'www.pimcore.org' ([Errno -5] No address associated with hostname)"))` - Domain was moved from .org to .com
This was referenced Mar 10, 2025
Merged
nodiscc
pushed a commit
that referenced
this issue
Mar 11, 2025
As part of #1 ERROR:awesome_lint.py: ARRCON: last updated -371 days, 1:31:33.390628 ago, older than 365 days Issues show lots of bugs No releases since 2023
This was referenced Mar 13, 2025
Merged
This was referenced Mar 21, 2025
This was referenced Mar 28, 2025
Rabenherz112
added a commit
to Rabenherz112/awesome-selfhosted-data
that referenced
this issue
Apr 5, 2025
- ref: awesome-selfhosted#1 - `ERROR:awesome_lint.py: Streama: last updated -366 days, 1:25:06.616775 ago, older than 365 days` - Last release was 2023 - tons of open issues
nodiscc
pushed a commit
that referenced
this issue
Apr 5, 2025
- ref: #1 - `ERROR:awesome_lint.py: Streama: last updated -366 days, 1:25:06.616775 ago, older than 365 days` - Last release was 2023 - tons of open issues
This was referenced Apr 7, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
This is a list of potentially unmaintained software projects and dead links in awesome-selfhosted.
Feel free to help fixing these issues by following the usual contribution process.
Remember that some projects are feature-complete/mature/simple enough that they don't need much maintenance. Check if they still have active users/work as advertised before removing them. You may notify the maintainer of each project in comments of your Pull Request, to inquire about the status of their project.
A summary of current problems can be found below and will be updated regularly. Please refer to the results of the latest daily automated checks for up-to-date information:

The text was updated successfully, but these errors were encountered: